Re: Supporting architectures without native C support (was Re: Meta-design)

2000-12-11 Thread Bradley M. Kuhn
Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote: [Re: Giving data about why it's hard to use B:: to port to the JVM] > Yes, *PLEASE*. Some hard data is always nice, even when (or especially > when) it's unpleasant to hear. I won't have "hard numbers", as it is always completely possible that some

Re: Supporting architectures without native C support (was Re: Meta-design)

2000-12-11 Thread Jarkko Hietaniemi
On Mon, Dec 11, 2000 at 08:18:05AM -0500, Joshua N Pritikin wrote: > On Sat, Dec 09, 2000 at 05:06:27AM -0500, [EMAIL PROTECTED] wrote: > > > Because the Python folks didn't have a problem basing JPython off of > > > CPython. > > > > Actually, this one isn't a good comparison. Python is substant

Re: Supporting architectures without native C support (was Re: Meta-design)

2000-12-11 Thread Joshua N Pritikin
On Sat, Dec 09, 2000 at 05:06:27AM -0500, [EMAIL PROTECTED] wrote: > > Because the Python folks didn't have a problem basing JPython off of > > CPython. > > Actually, this one isn't a good comparison. Python is substantially easier > to parse, and, is a much simpler language. I like Perl becaus

Re: Guaranteed object destruction (was Re: Meta-design)

2000-12-11 Thread Piers Cawley
Dan Sugalski <[EMAIL PROTECTED]> writes: > At 05:55 PM 12/7/00 +, Piers Cawley wrote: > >Dan Sugalski <[EMAIL PROTECTED]> writes: > > > I think I'd just as soon always call DESTROY in a predicable manner > > > and not do *anything* perlish at GC time. If nothing else it means > > > that we do