EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: VDCT expand and template constructs
From: Kay-Uwe Kasemir <[email protected]>
To: "Rees, NP (Nick)" <[email protected]>
Cc: [email protected], "Shepherd, EL (Emma)" <[email protected]>, Igor Verstovsek <[email protected]>
Date: Fri, 16 Dec 2005 12:51:46 -0500

On Dec 16, 2005, at 12:05 , Rees, NP (Nick) wrote:

conflict between
macros used as text substitution macros and macros used as port macros -
these are subtly different. If a port macro is not resolved then it
shouldn't be an error, I believe it should be treated as if it never
existed in
the first place. If a text substitution macro is not resolved then it
should remain as the macro to be substituted at a later time.

Hi Nick:

Not sure if I get this.
Are 'port' macros always output connections,
while 'text' macros are always inputs?

So 'text' or 'input' macros eventually need
a value, otherwise your database is pretty useless:
 field(SCAN, "$(TEXT_FOR_SCAN)")
 field(INP,  "$(TEXT_FOR_INP)")
Without SCAN, the record won't ever do anything,
without correct INP, it doesn't read anyting.

'Port' or 'output' macros allow a template to cause
additional processing or write to outputs:
 field(OUT,  "$(PORT_FOR_OUT)")
 field(FLNK, "$(PORT_FOR_FLNK)")
But you might be perfectly happy with the functionality
of a template without FLNK'ing it to other records.


Or is this beyond in/out direction?
Do you have an example of "input port" macros
that are still different from "input text"?


Some time ago, there was the XML question,
and one if not the key argument against was
lack of good macro support.
Does this requirement for two types of macros
fully eliminate XML?

Thanks,
-Kay


Replies:
Re: VDCT expand and template constructs Benjamin Franksen
References:
VDCT expand and template constructs Rees, NP (Nick)

Navigate by Date:
Prev: VDCT expand and template constructs Rees, NP (Nick)
Next: Re: VDCT expand and template constructs Benjamin Franksen
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: VDCT expand and template constructs Rees, NP (Nick)
Next: Re: VDCT expand and template constructs Benjamin Franksen
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·