A directive for selecting between "cwd first"
and "path(s) first" won't be sufficient, since
the -P option (which allows you to pre-include
files) results in %INCLUDE directives -- they
get processed before you could select.
So you would need a command line option. I was
too lazy to write that code... and too shy to
pick a letter for it. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The -I- used by GCC (-iquote actually, since -I- is
deprecated) has two effects: it splits the list of
include paths (#include "xx" vs #include <xx>), and
it prevents the directory containing the current file
from being searched.
The former has no equivalent in NASM, and the latter
is different (current file's vs CWD) from NASM.
That said, NASM needs two command line options: one
for controlling whether the CWD is searched first or
last (this request) and one for controlling whether
the CWD is searched at all (a Q4/2007 request).
I have attached an additional set of changes.
File Added: changes2.txt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No it doesn't, because once you have the former, the user can always add the CWD as an explicit option (-I or I./ or whatever is appropriate for their OS).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
necessary changes
Logged In: YES
user_id=73628
Originator: NO
I wouldn't mind a cl option and/or a directive, but, in addition to the problem of breaking existing code, I prefer the current behavior.
Logged In: YES
user_id=804543
Originator: YES
A directive for selecting between "cwd first"
and "path(s) first" won't be sufficient, since
the -P option (which allows you to pre-include
files) results in %INCLUDE directives -- they
get processed before you could select.
So you would need a command line option. I was
too lazy to write that code... and too shy to
pick a letter for it. :)
Logged In: YES
user_id=58697
Originator: NO
I suggest an option to reset the include path, *including* the implicit leading "-I." From what I've seen, this is often written "-I-".
Logged In: YES
user_id=804543
Originator: YES
The -I- used by GCC (-iquote actually, since -I- is
deprecated) has two effects: it splits the list of
include paths (#include "xx" vs #include <xx>), and
it prevents the directory containing the current file
from being searched.
The former has no equivalent in NASM, and the latter
is different (current file's vs CWD) from NASM.
That said, NASM needs two command line options: one
for controlling whether the CWD is searched first or
last (this request) and one for controlling whether
the CWD is searched at all (a Q4/2007 request).
I have attached an additional set of changes.
File Added: changes2.txt
additional changes
Logged In: YES
user_id=58697
Originator: NO
No it doesn't, because once you have the former, the user can always add the CWD as an explicit option (-I or I./ or whatever is appropriate for their OS).