From: groepaz (groepaz_at_gmx.net)
Date: 2001-12-11 20:40:01
Hello Ullrich, UvB> While handling of Unix paths is rather easy, since the notification is clean UvB> and orthogonal, DOS and Windows paths are a mess. There may be: UvB> 1. absolute paths without a drive UvB> 2. absolute paths including a drive UvB> 3. relative paths without a drive spec UvB> 4. relative paths including a drive spec UvB> 5. network paths using the \\server\share\sub\dir notification UvB> All these need different handling and platform dependent routines that are UvB> different from compiler to compiler because they are non standard (e.g. get UvB> the current drive, get the current path on another drive, and so on). mmmmmmh 1) at program start, get current working dir and remember that 2) whenever you want to access files from the current working dir (as in, from where the tool has been launched), or any paths relative to it, prepend the path remembered before. 3) whenever you access (read) a sourcefile, set current working dir to directory of that file 4) to avoid breaking existing code, always search current working directory last. i think that might even work in a portable way (getcwd/setcwd should be available everywhere no?) - well except a "collapsepath" functionality would be needed for "OSes" like ms-dos... just an idea that came to my mind (well you know you always think about totally unrelated things when supposed to do boring work...writing docfiles....*sigh* ;=)) -- Best regards, groepaz mailto:groepaz_at_gmx.net ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2001-12-14 22:05:44 CET