In the ideal multi-sourced compilation unit or file inclusion case, the
files would effectively be
concatenated together with whitespace (i.e. token-breaking) separators
at their junctions.
That is the plain meaning I get from the standard, but I did not find a
citation as direct as that.
Section 22.4 come closest to describing the intended effect.
Within that viewpoint, tools with trouble either parsing, or in this
case
preprocessing,
across such internal boundaries just have a bug.
Your use of the singular ("some other [tool] errors out") has me
cringing.
Greg Jaxon
Sourasis Das wrote:
Hi,
Should a macro call be allowed to split across multiple files ?
For example,
File a.v
---------
`define MAC(x) wire x
module top;
`MAC(
File b.v
--------
w);
endmodule
When the input order is "a.v b.v", I can find some standard tools pass
it while some other
errors out while parsing.
I do not find LRM to explicitly allow/restrict it anywhere.
Thanks,
Sourasis
--
This message has been scanned for viruses and
dangerous content by
MailScanner, and is
believed to be clean.
Received on Thu Jun 3 09:46:17 2010