Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problem Event Name BEX
Message
De
29/05/2015 02:42:48
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
 
À
29/05/2015 02:34:48
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MySQL
Application:
Desktop
Divers
Thread ID:
01620116
Message ID:
01620311
Vues:
64
>>>Dennis,
>>>
>>>In any reason get rid of the return within a with..endwith statement, if it does not result in a C00005 error now it will end up the next day.
>>>Rgds,
>>>Koen
>>>
>>>
>>
>>That's strange. I never run into this and I must have RETURN inside WITH .. ENDWITH countless times. I feel uncomfortable now.
>
>We had quite a few of those until my coworker back then ran into the situation, that the datatype of the returned variable was not correct.
>She called me over, we both stared rather unbelieving at the screen. I played with the code for 30 min to make certain it was not just a side effect of something goofy done before but overlooked, but found nothing. Returning the same variable at the end of the method resolved the glitch.
>
>So a large project had to be cleaned afterwards - I still remember writing some code to flag suspicious early returns and compare the lineno with the last endwith.

I think I will have to look at this. I have code somewhere to look for non-end-returns and multiple returns. But it is so fine code obfuscation. You know, make things look like they go all on through a end-of-method-return and then jump out inbetween :(
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform