Re: An interesting observation that emerged at lunch

[one last time, for John]

ht writes:

>   2) New ones: XProc language port variables, bound with various arrows.

If we thought about (2) as naming pipes, not ports, then we might think
of changing

  $in -> xinclude() >> $temp
  $temp >> "included.xml"

to something a little clearer. We call 'temp' a *pipe name*,
and write the above this way

  $in -> xinclude() >> @temp
  $temp >> @"included.xml"

where $temp is the name for the downstream end of the pipe named
'temp' and @temp is the name for its upstream end.

We can go on to play with the characters, and where they go:

  in$ -> xinclude() >> @temp
  temp$ >> @"included.xml"

or even

  in> -> xinclude() >> >temp
  temp> >> >"included.xml"

At which point either the -> or the > is redundant:

  in> xinclude() >temp
  temp>  >"included.xml"

or

  in-> xinclude() >>temp
  temp->  >>"included.xml"

Fun with plugs and sockets!

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

Received on Thursday, 11 February 2016 15:15:29 UTC