From: Stefen Boyd (stefen@boyd.com)
Date: Wed Apr 15 1998 - 09:32:59 PDT
At 03:56 PM 4/15/98 -0000, you wrote:
<p>BAD MSG:
>
A very good point. Another ugly feature of `timescale is that it can
>appear anywhere inside a module. I am not sure if it means that the
>current module is affected or only the next one. It would be much
>cleaner to limit it to appear only between modules.
>
X-Lines: 30
Content-Type: text/plain; charset="us-ascii"
Content-Length: 538
X-Status: $$$$
X-UID: 0000000385
Status: RO
I suppose we could have a `module_timescale, but to keep
user confusion down and maybe even make parsing easier?
how about:
module foo(a,b,z);
timescale 1ns/100ps;
input a,b;
output z;
endmodule
The timescale is allowed to appear as a module item.
The downside is a new keyword, but the upside is that
it is clearly scoped to the module.
Stefen
<p>--------------------
Stefen Boyd
__
| \ ____
|_/_ |
| \ |__
|___/oyd |
|___nterprises
stefen@boyd.com
(408)739-BOYD
(408)481-9658 (fax)
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:52:48 PDT
and
sponsored by Boyd Technology, Inc.