From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2001-12-11 13:08:02
Hi!
On Mon, Dec 10, 2001 at 07:57:26PM +0100, groepaz wrote:
> what do these guidelines say about how to name include files then? (it
> kinda makes having several files with the same name a lottery ..... hu
> which one will be included this time? ;=))
Obviously, include files cannot have the same names when using -I, at least
not, when both may be used at once.
> mmmh break existing code? how? wouldnt old code work just the same?
Files may be found were no files were found before and vice versa. Depending
on the search algorithm actually implemented even other files may be found if
they have the same name. This is because -I guarantees that the search order
is exactly the order of the paths specified (with the exception of the builtin
paths).
> yes, surely, for a clean working implementation you need "expandpath"
> and "collapsepath" - which kinda need to be target-specific (well
> they'd have a handfull minor tweaks in #ifdef 's i'd say ;=))
While handling of Unix paths is rather easy, since the notification is clean
and orthogonal, DOS and Windows paths are a mess. There may be:
1. absolute paths without a drive
2. absolute paths including a drive
3. relative paths without a drive spec
4. relative paths including a drive spec
5. network paths using the \\server\share\sub\dir notification
All these need different handling and platform dependent routines that are
different from compiler to compiler because they are non standard (e.g. get
the current drive, get the current path on another drive, and so on).
Regards
Uz
--
Ullrich von Bassewitz uz_at_musoftware.de
----------------------------------------------------------------------
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