Someone's been busy...
On Mon, 25 Sep 2000, Simon Cozens wrote:
> Data which comes in through a line discipline B be in UTF8, unless
> C is in force.
{snip}
> C just throws everything. None of the above happens.
What does "just throws everything" mean?
In RFC 294, data is internally stored in
On Mon, Sep 25, 2000 at 10:08:38PM +0100, Simon Cozens wrote:
> On Mon, Sep 25, 2000 at 02:01:10PM -0700, Ask Bjoern Hansen wrote:
> > WORKING GROUP: perl6-internals-unicode
> > CHAIR: Simon Cozens <[EMAIL PROTECTED]>
> > DEADLINE:
>
> 16th October, extended if required
Please ignore me. I am a
On Mon, Sep 25, 2000 at 02:01:10PM -0700, Ask Bjoern Hansen wrote:
> WORKING GROUP: perl6-internals-unicode
> CHAIR: Simon Cozens <[EMAIL PROTECTED]>
> DEADLINE:
16th October, extended if required
> MISSION:
World dom.. oh, uhm.
Discuss RFCs 294, 295, 296, 300, 312, 313 and related RFCs. Repor
On Tue, Sep 26, 2000 at 01:19:16AM +0200, Bart Lateur wrote:
> Eh? Are you saying that Perl's error message should be adapted to the
> language of the computer user? I don't like that.
That's precisely what I am saying, yes, but I'm not wedded to the idea as a
religious principle. I think it woul
Bart Lateur <[EMAIL PROTECTED]> writes:
> Eh? Are you saying that Perl's error message should be adapted to the
> language of the computer user?
Yes. Most major free software packages already do this.
> I don't like that.
You can always not set the environment variables.
> How would Perl dec
Michael Maraist <[EMAIL PROTECTED]> writes:
> I suggested this a while ago, and the response was that automatically
> writing files is a security risk. You should extend your RFC to
> describe a caching directory or configuration.
This will be completely impossible to implement in some installa
On 25 Sep 2000 20:15:19 -, Perl6 RFC Librarian wrote:
>Erreur de syntaxe. Syntaxfehler. Errore di sintassi. suntaktik'o sphalm'a.
>
>Perl 6 needs some kind of internationalisation and therefore message
>catalogue support. Really needs, with great urgency.
Eh? Are you saying that Perl's error
> C should be renamed to C for Perl 6, and
Heh. I'm working on an integrated tie proposal right now that uses this
exact notion - and even a C naming scheme! I guess I'll be
referencing your RFC... ;-)
-Nate
On Mon, Sep 25, 2000 at 05:35:09PM -0400, Michael Maraist wrote:
> In general, however, I don't see bytecode reading as being the real
> bottle-neck.
Quoting Nick Ing-Simmons in
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-05/msg01122.html:
"I have had similar doubts for some
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:Provide multiple sort algorithms, and have a pragma select which Perl
:uses; when a program is being compiled, analyze the data and
:heuristically select the better algorithm if possible.
Analysing at compile time seems real difficult. It would
Simon Cozens <[EMAIL PROTECTED]> formally RFC'd:
> I have no idea how to implement tail recursion elimination, and I'd
> dearly love to learn. Unrolling loops with constant indices shouldn't be
> too hard.
AIUI you trigger your destructors on the appearance
of the "return" keyword rather than
> Ordered bytecode
>
> Bytecode should be structured in such a way that reading and executing
> it can be parallelised.
>
Are you suggesting a threaded VM? I know that the core is being rewritten,
so it's a possibility. If this is the case, then you'll want to reference
some of the other RFC's
At 02:01 PM 9/25/00 -0700, Ask Bjoern Hansen wrote:
>On Mon, 25 Sep 2000, Dan Sugalski wrote:
> > Ask, can you set up perl6-internals-unicode please?
>
>Sure. Fill in the blanks:
>
>WORKING GROUP: perl6-internals-unicode
>CHAIR: Simon Cozens <[EMAIL PROTECTED]>
>DEADLINE:
Oct 28, 2000
>MISSION:
> So, we check for the existence of a C<.plc> file before running a
> program; if the C<.plc> file is newer than the program, we use that
> instead. If there isn't a C<.plc> file or it's older than the program,
> recompile and dump the bytecode to a C<.plc> file. Naturally, this gives
> us the bes
On Mon, 25 Sep 2000, Dan Sugalski wrote:
> At 09:34 AM 9/25/00 +0100, Simon Cozens wrote:
> >Dan,
> > I've finally woken up and I now have 8 RFCs on Unicode handling[1] I'm
> >about to throw at the librarian. While I'm perfectly happy to have them
> >disgust (sic.) here, I think it might be s
At 09:34 AM 9/25/00 +0100, Simon Cozens wrote:
>Dan,
> I've finally woken up and I now have 8 RFCs on Unicode handling[1] I'm
>about to throw at the librarian. While I'm perfectly happy to have them
>disgust (sic.) here, I think it might be sensible to start up a WG for
>discussing Unicode Thi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C and C
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 300
Version: 1
Status: Developing
=head1 ABSTRACT
Perl 5.6's C is
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Kick out all ops - libprt
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 315
Version: 1
Status: Developing
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
A parser is a many-layered thing
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 314
Version: 1
Status: Developing
=head1 A
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl 6 should support I18N and L10N
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 313
Version: 1
Status: Developing
=head
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Unicode Combinatorix
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 312
Version: 1
Status: Developing
=head1 ABSTRACT
How
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Ordered bytecode
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 310
Version: 1
Status: Developing
=head1 ABSTRACT
Bytecod
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C algorithm to be selectable at compile time
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 304
Version: 1
Status: Developi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Keep C, but make it work.
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 303
Version: 1
Status: Developing
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Unrolling loops and tail recursion
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 302
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Cache byte-compiled programs and modules
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 301
Version: 1
Status: Developing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Attributes for compiler hints
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 297
Version: 1
Status: Developing
=head1 ABST
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Getting Data Into Unicode Is Not Our Problem
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 296
Version: 1
Status: Developi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Normalisation and C
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 295
Version: 1
Status: Developing
=head1 ABSTRACT
Perl
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Internally, data is stored as UTF8
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 294
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
MT-Safe Autovariables in perl 5.005 Threading
=head1 VERSION
Maintainer: Michael Maraist <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 293
Version: 1
Status: Deve
Here are a few comments on RFC35 (base format for perl variables).
[ NB - I've only just joined this list, and although I've rummaged
through the archives, I may have missed bits which make my comments
obsolete/absurd etc... :-) ]
1. void *variable_data;
I would suggest having a slightly larger
Dan,
I've finally woken up and I now have 8 RFCs on Unicode handling[1] I'm
about to throw at the librarian. While I'm perfectly happy to have them
disgust (sic.) here, I think it might be sensible to start up a WG for
discussing Unicode Things. I'm even fool enough to volunteer to chair it i
33 matches
Mail list logo
