RE: DocBook function synopsis

[Graydon Hoare <graydon@xxxxxxxxxxxxx>]

> Actually, it later occurred to me to use the a declaration like the 
> following instead
> 
> <!ENTITY % local.funcdef.attrib "
>   Class CDATA #IMPLIED
>   Abstract (abstract|concrete) concrete     -- pure or not --
>   Dispatch (dynamic|static) static          -- virtual or not --
>   Effect (functional|imperative) imperative -- const or not --">
> 
> which I think is clearer, since it avoids the eccentricities of C++
> terminology.  Anyway, the specific names are still not decided.

you might want to throw in "Evaluation (lazy|strict) strict" in case
you have someone who wants to docbook some haskell code. For that
matter (totally barging on in the subject here) does the current
function synopsis have elements to describe type variable paramteres
or pre/post conditions?

-graydon


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