Experimental Physics and
Industrial Control System

Benjamin Franksen <[email protected]> · Fri, 16 Dec 2005 19:20:23 +0100

On Friday 16 December 2005 18:51, Kay-Uwe Kasemir wrote:
> 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?
>
> [...]
> 
> Or is this beyond in/out direction?

I think you misunderstood the point. The way in which port macros have 
an opposite direction compared to normal macros is in the way they are 
resolved. To quote from the link Nick gave:

"Hierarchical templates as implemented by VisualDCT must allow macro 
values to be passed into the template instance (giving values for 
fields within the expanded template), and values to be exported from 
the template instance to the higher level (usually the destination 
field name for a link in a record defined in the higher level .vdb 
file)."

Ben

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System