Subject: Re: [sv-ec] System Include Proposal - Version 2
From: Stephen Williams (steve@icarus.com)
Date: Thu Mar 13 2003 - 11:11:53 PST
> - I believe if you are introducing a C-like feature, you should
> follow C-like practice as well. Maybe even extract the description
> from the C standard?
>
> So far I've found 3 different definitions of how this works with GNU,
> Visual Studio, and SunWSPro. If there was one consistent definition I
> would agree with this comment whole heartedly, but alas there is not
> one. I've simplified the proposal so that <> only searches the system
> include area.
Just to clarify, all 3 C compiler examples you gave will extend the
<file> search path with a -I flag to the command line compiler. Yes,
even the MicroSoft command line compiler "cl" takes a "-I" flag. The
location of the system header files varies with all three, but all
search the system header directories *last*, after those directories
added by -I switch.
How does this relate to SystemVerilog and `include? Library vendors
are presumably going to want to place their header files in a common
place that is *not* the Cadence/Synopsys/FlyByNight specific place,
but a library specific place. The library vendor will then want to
make those header files available to programmers using `include <foo>
and some vendor specific means to add the library vendor directory
to the tool search path.
Your wording specifically denies this possibility:
> When the angle bracket ("<>") notation is used, then only the vendor
> defined location containing files defined by the language standard is
> searched.
This specifically excludes third-party libraries?
-- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, steve at picturel.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
This archive was generated by hypermail 2b28 : Thu Mar 13 2003 - 11:13:59 PST