[Prev][Next][Index][Thread]
Re: New Lisp ?
-
To: info-dylan@ai.mit.edu
-
Subject: Re: New Lisp ?
-
From: "Olivier Lefevre" <Olivier.Lefevre@genedata.com>
-
Date: Fri, 28 Dec 2001 11:45:02 -0500 (EST)
-
Organization: GeneData AG
-
References: <slrna2acon.8d1.markj+0111@cloaked.freeserve.co.uk> <c571739c.0112222317.3d2be7fd@posting.google.com> <slrna2b8q0.1bm.markj+0111@cloaked.freeserve.co.uk> <c571739c.0112230535.2dd6f1b1@posting.google.com> <scoc2u4qkpue4mt9irr0cldu5ig913qogr@4ax.com> <l91d2ucqplfm9auo2gi20pd74ktnl2utlp@4ax.com> <ni8f2uck3ua78ucps9kg9c4sal2g38r85v@4ax.com> <87vgew4631.fsf@teonanacatl.andreas.org> <3C27C7BC.DECCE7DB@quiotix.com> <87pu542jjz.fsf@teonanacatl.andreas.org> <3C27D85C.9E5FE363@quiotix.com> <Pine.A41.4.21L1.0112251208250.33498-100000@login9.isis.unc.edu> <87d7133y8o.fsf@teonanacatl.andreas.org>
-
Xref: traf.lcs.mit.edu comp.lang.dylan:13889
> One instance where sealing really helps is arithmetics. Witness Java
> for a language that gives up it's OO approach for fast integers, and
> the problems this introduces.
Actually I believe Gosling said somewhere (in one of his many interviews)
that primitive types were added at the eleventh hour because of a perception
that "wrapped" number types couldn't possibly be fast. They did make all
such
types final, so they would probably concur with all the nice things you say
about sealing but they felt they had to heed that prejudice: at the time,
Java was still only a blink in their eye, not the juggernaut it is now,
and, who knows, that could have been the kiss of death.
I wonder how Integer vs. int etc affects memory footprint, though.
-- O.L.
References: