Hi,
Since directory("c:\path","d") returns an array of 1 element, my friend used directory("c:\path\","d") to get list of directory for years. He did it in Clipper, and after that he successfully did it in xHarbour.I've looked to xHarbour's code, they have code to mask platform dependent behavior:if ( pFileName[iNameLen-1] == OS_PATH_DELIMITER ) // '\\' { strcat(pFileName,"*.*") ; // 26/01/2004: Clipper compatibility }We may try to mask these platform differences in Harbour code (controlled with some more SETs), but I'd rather suggest to modify the call to be more platform independent.I don't thing we need some set, we just need to a few lines like above of code to mask platform dependent behavior.I'm not sure if this is right, or future proof. In Harbour we cover all such cases with SETs, because not everyone wants to leave any filename messing to Harbour, and the whole issue is mostly relevant for legacy apps; for new or updated ones, it's not always good or desired. Notice that it's also hard to tell (without testing) whether Clipper behaves the same way under plain DOS, other DOS flavors, and Windows.
It's easy to tell: Clipper behaves the same, because this case is managed by Clipper DIRECTORY() function. See, below.
Maybe this works, but it's easy to find a parameter which
would behave differently depending on the platform, enough
to think about casing, drive letters, or any other speciality
(like special chars).
See the discussion on trimming filenames last week or so.
(File(" myfile.txt") or something like this)
I do not see here relation to spaces or upper/lower case filenames. Spaces and upper/lower case letters are valid in some OS, but not DOS. Since Clipper was written for DOS only, we must solve this aspect for other OS by SET's. Here is different question, every OS has path separator, and we must list all files if last character is path separator. What SET's do you propose?
I still think it's not Harbour's job, to present a "virtual FS" with fully MS-DOS compatible rules. Or even if want such thing, it should be an option.
I've tested what strings are passed to DOS. The same results in directory(".../") and directory(".../*.*") function calls are obtained because Clipper adds *.* if last character is path sepatator. So, it's not a question of platform behavior, it's Clipper.
Best regards, Mindaugas _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
