Re: [caplisp-devel] Greetings caplisp denizens!

[David M. <ra...@gm...>]

On 8/25/05, Mark Miller <ma...@cs...> wrote:
>=20
> David Mercer wrote:
> > And then there have been an occasion or two where I failed to
> > communicate an idea clearly enough, got pooh-poohed or ignored, and
> > saw the idea come back around a year or more later in new clothes and
> > be hailed as wonderful. Ah well, live and let live!
>=20
> Happens to all of us repeatedly. I've lost count myself. I've also=20
> committed
> this sin myself, and I always appreciate when someone lets me know. When=
=20
> such
> an occurrence happens, whether to you or anyone else, please post a
> clarification and a link to the earlier expression of the idea. That's on=
e=20
> of
> the wonderful benefits of having a permanent public archive!


I'll google up my ODNS post(s) and the relevant VLS/httpys bits that are=20
comparable
for posting to the appropriate list(s)....but probably not right now, as I=
=20
still intend to=20
further extend httpys in a (compatible) way with the ODNS features that are=
=20
not in
the current httpsy spec/implementation (basically "rooted" vs. "unrooted"=
=20
httpsy hashes).
Lord, I suppose I need to go and see if Tyler has any list(s) for httpsy an=
d=20
friends, or
is all that on captalk?

> Hhmmm, in that case I think that perhaps "caplisp" is more precise
> > than I'd even intended, since it is object level security that will
> > require (perhaps) modifications to the guts of lisp itself, rather
> > than being purely extensions.
>=20
> If you want the project's name to align this work with CaPerl or CaPython=
,
> perhaps you should consider CaLisp? Only a suggestion.


Naw, I think that they got lucky in having a first letter of "P" so that CA=
P=20
is the
beginning of the name! And CaLisp looks like something from canada or=20
california!=20

**bit snipped**
>=20
> > If so, then I am indeed starting work on caplisp, James appears most
> > interested in Lisp-E (which I did consider, having remembered your
> > above referenced note!) before I created the project, and Kevin of
> > course has already made quite a start on E-on-CL! I imagine much code
> > can/will be cross polinated, and James is welcome to host
> > code/lists/webpages on the caplisp sourceforge project space if he'd
> > rather not deal with the (minor) fuss and bother of setting up a
> > seperate home for Lisp-E (or would CLisp-E be preferred?)
>=20
> This is a good clarification. Could you post something along these lines=
=20
> to
> caplisp? Thanks.


Wil do!=20

> Oh yes, whomever had the idea to grab the coinage "object
> > capabilities" hit the nail on the head. My god, how many endless
> > threads and re-hashings did it take for that term to emerge? :-)
>=20
> Yup, that was painful.


Well I do think that the struggle merely enphasizes the worth of what came=
=20
out of it.
"Object capabilities" has been great shorthand to immediately Not Confuse=
=20
unix/security
people I've talked to who have been exposed to prior/other uses of the term=
=20
"capability" in a meaning other that what we mean completely. Then comparin=
g=20
that to
a unix file descriptor and you're all the way home and that 'get it'.

> > I think I thought things out on the keyboard pretty well above, thanks
> > very much for the nomenclature clarification, it was essential!
>=20
> You're welcome!
>=20
> --
> Text by me above is hereby placed in the public domain
>=20
> Cheers,
> --MarkM
>=20
>=20
Cross-posted to caplisp, hope you don't mind! (See your license above! :-)

-David Mercer
Tucson, AZ

--=20
"Nothing above represents the position or opinion of the University of
Arizona or the Dept. of Mathematics, so there! :-)"