Thanks,
-- eliot
... you're posting a Scheme problem in a Common Lisp newsgroup. :)
#:Erik
;* "E. Handelman" <el...@generation.net>
;| The obscure problem is that ...
;
; ... you're posting a Scheme problem in a Common Lisp newsgroup. :)
;
;#:Erik
Aha, but the newsgroup name doesn't specify Common Lisp, if I may speak
here as a schemer.
-- eliot
however once with common roots, Lisp and Scheme have developed entirely
different cultures and user communities, so there's not much to share
between them, anymore. that's probably the best reason other Schemers
didn't want their newsgroup called comp.lang.lisp.scheme, so check out
comp.lang.scheme.
#:Erik
> In article <31493779...@naggum.no>, Erik Naggum <er...@naggum.no>
> wrote:
>
> ;* "E. Handelman" <el...@generation.net>
> ;| The obscure problem is that ...
> ;
> ; ... you're posting a Scheme problem in a Common Lisp newsgroup. :)
> ;
> ;#:Erik
>
> Aha, but the newsgroup name doesn't specify Common Lisp, if I may speak
> here as a schemer.
The comp.lang.c newsgroup name doesn't specify ANSI C, and they'll
flame you away if you ask about sockets, threads, Unix/Windows
programming, whatever--anything not ANSI C.
We don't just discuss ANSI CL here though, we also discuss
multiprocessing, the MOP, etc. We don't usually discuss Scheme, unless
we are criticizing it, however. So you would probably find c.l.scheme
and the MacGambit maintener/tech-support people more useful.
Christopher
; We don't usually discuss Scheme, unless
;we are criticizing it, however. So you would probably find c.l.scheme
;and the MacGambit maintener/tech-support people more useful.
He was, as it happened. I'm also well aware of the differences between
scheme and CL. I apologize for the intrusion.
-- eliot