Re: DD: ports -Reply

[Sebastian Rahtz <s.rahtz@xxxxxxxxxxxxxx>]

 > Probably a very simple explanation Sebastian,
 > Port is the opposite of starboard isn't it?
no, its a fortified wine from Northern Portugal....

 > We (the beginners) need to be told it _needs_ to be
 > in DD before it gets included.
...
 > Which chapter please?
 > _and_ could / would you author it?

it belongs at the same level as `what is a flow object', i think. in
fact, its part of `what is a flow object'.

i wish i _could_ author it. i am afraid ports baffle me. i would not
even have met them, were it for having to do math. thus when i come
to process my <FR> (fraction) element, I do

(element fr
 (make fraction
   (process-children-trim)
 )
)
(element nu
      (make math-sequence
         label: 'numerator 
   (process-children-trim)
))

(element de
      (make math-sequence
         label: 'denominator
   (process-children-trim)
))

ie the <DE> and <NU> rules attach themselves like leeches to the
fraction FO I created for <FR> (the fraction FO has predefined ports
called numerator and denominator)

so i know what to do empirically, but i don't think this a rational
explanation of what problems ports[1] solve

Sebastian

[1] apart from being good places to dock ships, of course

 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist