[Fwd: RE: Expressions as part of port connections in module instantiations]

From: David Miller <David.L.Miller_at_.....>
Date: Mon May 11 2009 - 09:34:36 PDT
Forwarded comments from Bob Floyd - silvaco

-------- Original Message --------
Subject: RE: Expressions as part of port connections in module instantiations
Date: Mon, 11 May 2009 09:12:15 -0700
From: Bob Floyd <bob.floyd@silvaco.com>
To: David Miller <David.L.Miller@freescale.com>

David,

Sorry, I don't participate often enough to have the proper instructions on
how to post. Feel free to
post it on my behalf if you wish.  Here are my comments.

>     child ch1(V(a))
>
> - and I would say that the latter is a signal-flow connection of the
> voltage of node 'a' (a PWL real value), as such it does not require an
> A2D. Any digital process sensitive to the port in ch1 (assign/@) gets an
> event at acceptance if V(a) changes.
>

"if V(a) changes" and "does not require an A2D" is an oxymoron:

For a variety of reasons, the numeric values in the solution vector at
adjacent timepoints is almost always different.

Without an A2D to threshold analog data, it can only be said "V(a) changes".
No "if" about it.  The A2D thresholding allows the "if".


Therefore, with regard to frequency of evaluation,

      child ck1(V(a))

is equivalent to

      child ck1(a)

Or, looking at child:

      module child(in);
        input in;
        always @in begin
           do something with in
        end

is no different than

      module child(in);
         input in;

         analog begin
           do something with in
         end

Because "always @in" will trigger at every time-point just as the analog
form does.

So why complicate the language to support "child ch1(V(a))" ?

Bob Floyd


>



-- 
==============================================
-- It's a beautiful day
-- Don't let it get away
--
-- David Miller
-- Design Technology (Austin)
-- Freescale Semiconductor
-- Ph : 512 996-7377 Fax: x7755
==============================================

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon May 11 09:35:27 2009

This archive was generated by hypermail 2.1.8 : Mon May 11 2009 - 09:35:42 PDT