🚀 go-pugleaf

In article <289@smds.UUCP> sw@smds.UUCP (Stephen E. Witham) writes:
> To me, the "power" of a language has to do with what concepts you can express
> DIRECTLY.

But what's direct? Why are pointers to functions direct, if pointers to
structures containing blah blah blah are indirect? I think this gives
you the same problem as trying to qualify ``has.''

I prefer to keep ``power'' an objective term, and to qualify it with
further objective terms: memory use, run time, code complexity (by any
sensible measure), etc. Words describing syntax can be objective too,
though I prefer to keep them well separated from the syntactic terms.

  [ function composition routines ]
> The question I'm interested in is, given that you hide the right stuff in
> include files and subroutine libraries, how TWISTED is this method to use
> in the places where you'd want "first class, composable, anonymous functions?"

Looks like it works to me, and it's not sufficiently twisted that I
wouldn't use it.

---Dan