As the message says. Code freeze tonight at midnight EDT (GMT-0400).
I'll be tagging with PRE_REL_0.0.7 then.
Features to be included:
Perl 6 grammar
Partial perl6 compiler
Pure-perl assembler
Heavily patched and upgraded intermediate language
Massive patching in general, cleaned-up PMCs.
FORTH
Austin Hastings:
# --- Dan Sugalski <[EMAIL PROTECTED]> wrote:
# > At 8:30 AM -0400 7/16/02, Karl Glazebrook wrote:
# > >I still feel this adds yet another layer of inconsistency and
# > >confusion. I can't look at a piece of code and know what it does,
# > >without referring up N lines to the to
At 12:34 PM -0400 7/17/02, Mark J. Reed wrote:
>On Wed, Jul 17, 2002 at 12:13:47PM -0400, Dan Sugalski wrote:
>> I thought Java used UTF-16. It's a variable-width encoding, so it
>> should be fine. (Though I bet a lot of folks will be rather surprised
>> when it happens...)
>UTF-16 isn't techni
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 8:30 AM -0400 7/16/02, Karl Glazebrook wrote:
> >I still feel this adds yet another layer of inconsistency and
> >confusion. I can't look at a piece of code and know what it does,
> >without referring up N lines to the top of the scripts.
> >
> >
On Wed, Jul 17, 2002 at 12:13:47PM -0400, Dan Sugalski wrote:
> I thought Java used UTF-16. It's a variable-width encoding, so it
> should be fine. (Though I bet a lot of folks will be rather surprised
> when it happens...)
UTF-16 isn't technically a variable-width encoding, since
surrogate code
On Wed, Jul 17, 2002 at 04:17:15PM +0100, Nicholas Clark wrote:
> My understanding was that Unicode has now escaped the base plane (or whatever
> it's called) and now has started using code points >65536. How does Java
> cope with this?
This is getting a little off-topic, I think. But here's a br
At 4:17 PM +0100 7/17/02, Nicholas Clark wrote:
>On Wed, Jul 17, 2002 at 12:32:43AM -0400, Mark J. Reed wrote:
>> On Tue, Jul 16, 2002 at 05:42:18PM -0400, Michael G Schwern wrote:
>> > I don't know how Java and Python handle Unicode.
>> Java has always been 100% Unicode from the ground up; it'
On Wed, Jul 17, 2002 at 12:32:43AM -0400, Mark J. Reed wrote:
> On Tue, Jul 16, 2002 at 05:42:18PM -0400, Michael G Schwern wrote:
> > I don't know how Java and Python handle Unicode.
> Java has always been 100% Unicode from the ground up; it's in the spec.
> The fundamental char type is a 16-bit
