[Prev][Next][Index][Thread]

Re: New Lisp ?

Jeffrey Siegal <jbs@quiotix.com> writes:

> What happens in Java is that you have to at least declare the exceptions
> up the chain anyway (the compiler will reject a method that doesn't

Yes, and that bothers me to no end.  I want to have specific code that
knows about an exception in exactly two places: where it is generated,
and where it can be handled.  All the code inbetween doesn't need to
know more than that an operation has failed and that it needs to clean
up.

> Yes and no.  They're not "regular objects" because they can't be
> subclassed. 

That's true.  The point of sealing is to offer the option of turning
off certain OO features while retaining the benefits of others (the
user can still specialize his own generic functions on integers, for
instance).

> I think what you'd see in any kind of production
> environment if Dylan were used is that almost everything would get
> sealed off, much the way a lot of Java code makes extensive use of
> "final."  At that point, you might as well just use a static block
> compiler and let the compiler recognize what is subclassed and what
> isn't.

I'd hate to use a static block compiler, the turnaround time would be
a nightmare.  And I'd like to keep the option of adding classes and gf
methods at runtime.

Adreas

-- 
"In my eyes it is never a crime to steal knowledge. It is a good
theft. The pirate of knowledge is a good pirate."
                                                       (Michel Serres)
Follow-Ups: References: