Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to restore the DEBUGOUT accurately?
Message
De
20/01/2009 18:58:03
 
 
À
20/01/2009 04:10:02
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01375106
Message ID:
01375754
Vues:
7
G'day.

My understanding is that you are trying to restore the setting back so that it is as if it was never turned off. In that case you have to always use the Additive clause. If you don't then anything that your program has written into the log before your routine runs will be destroyed. When you use Set DebugOut or Coverage normally you do have to choose if you want Additive or not, but because what you are trying to do here is restore the setting you must use the Additive option to prevent the data you have already written from being destroyed. As soon as you execute a Set Debugout or Coverage statement without the Additive clause the log file is emptied, which is obviously not what you want if you are trying to make your routine transparent.

Ian Simcock.


>>Howdy.
>>
>>When you restore it you'd have to use the Additive clause every time in order to make it work properly. If you dont then anything that had been written to the logs before you switched it off will be lost. Additive basically means that the current content of the log file is not to be destroyed, which will always be what you want if you are trying to set things back the way that they were.
>>
>>Ian Simcock.
>>
>>
>>>Hi,
>>>
>>>The SET() function only gives the filespec of
>>>
>>>SET DEBUGOUT|COVERAGE TO filespec [ADDITIVE]
>>>
>>>but it won't tell me whether the ADDITIVE clause is used or not used...
>>>
>>>Is there no chance for me to save and restore accurately the DEBUGOUT and COVERAGE settings, taken into account the ADDITIVE clause?
>
>IMO, the ADDITIVE clause is optional because we sometime need to omit it.
>If I always SET DEBUGOUT with the ADDITIVE clause, then I got no way to wipe whatever captured in the file and start all over again, unless I change to another output file (which I normally won't want to).
>
>In fact, I don't have problem understanding how to use the SET command with respect to the ADDITIVE clause, my concern is to know how (or it is possible) I can programmatically determine whether or not the ADDITIVE clause is used in the last execution of the either of the above commands.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform