Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Getfile question
Message
De
31/03/2000 19:38:57
 
 
À
31/03/2000 19:14:37
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00353361
Message ID:
00353753
Vues:
29
>Ed-
>
>>>>save a little effort - FULLPATH(CURDIR()) will return the current directory properly prefixed without the ambiguity that I've seen arise from using SYS(5) on UNCs where you're working in an unmapped UNC, and terminates cleanly with the \ in all cases.
>
>Great point on using FULLPATH. But, in trying to make sure I understand _all_ your points in this, I find there seems to be no difference between:
>
>
?fullpath(curdir())
>?fullpath(sys(5)+sys(2003))
The issue is SYS(5) and UNCs; I don't have all my notes here, but SYS(5) behaves poorly in some network situations where you're sitting on an unmapped UNC. SYS(2003) is always fully qualified; I'm arguing against the use of SYS(5) at all, and if you're simply getting the current directory on the current drive, FULLPATH(CURDIR()) is more human-readable than FULLPATH(SYS(2003)) and more self documenting, and both work equally well (yeah, why should this matter?) I'd argue just as vehemently against SYS(5)+CURDIR()...
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform