=head1 IMPLEMENTATION
Tricky.
Perl needs to know about scalar context, list context, and "finite
list" context. Presumably, if I/O routines behave this way, user
subs should be able to behave this way as well. Might use the same
machinery as lazy subs.
RFC 21
This begs a question - How would this be implemented, knowing that at least
some MAJOR modules have what I call "run-time" dependencies, which are very
easy to do with Perl?
For example, what would this option think of DBI, for example, with it
loading DBD's based on subroutine parameters?
Or,
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Compilation: Remove requirement for final true value in require-d and do-ed files
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 7 Aug 2000
Last Modified: 25 Sep 2000
Mailing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Higher order functions
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 4 Aug 2000
Last Modified: 25 Sep 2000
Number: 23
Version: 6
Mailing List: [EMAIL PROTECTED]
Status:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Core support for method delegation
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 4 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 193
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Subroutines: Extend subroutine contexts to include name parameters and lazy arguments
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 17 Aug 2000
Last Modified: 25 Sep 2000
Mailing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Private keys and methods
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 1 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 188
Version: 3
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects: Cuse invocant pragma
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 14 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 223
Version: 2
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Fix iteration of nested hashes
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 18 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 255
Version: 3
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Native support for multimethods
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 18 September 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 256
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Builtins : Make use of hashref context for garrulous builtins
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 19 Sep 2000
Last Updated: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Subroutines : Pre- and post- handlers for subroutines
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 21 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
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:
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
Normalisation and Cunicode::exact
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 295
Version: 1
Status: Developing
=head1
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:
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
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Make subroutines' prototypes accessible from Perl
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 298
Version: 1
Status:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C@STACK - a modifyable Ccaller()
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 299
Version: 1
Status: Developing
=head1
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
Keep Cuse less, 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
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Csort 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:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Ban Perl hooks into regexes
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 308
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Allow keywords in sub prototypes
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 309
Version: 1
Status: Developing
=head1
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
Bytecode
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Line Disciplines
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 311
Version: 1
Status: Developing
=head1 ABSTRACT
BThis is
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
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
=head1
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
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
Cuse unicode::representation and Cno unicode
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 300
Version: 1
Status:
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 Things.
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implicit counter in for statements, possibly $#.
=head1 VERSION
Maintainer: John McNamara [EMAIL PROTECTED]
Date: 16 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number:
Add a new special variable, C@STACK to replace the Ccaller()
function. Allow people to modify the call stack in certain, very
restricted ways.
Perl 6 = Perl 5
$STACK[-1] = [caller(0)];
$STACK[-2] = [caller(1)];
I strongly agree with the opinion that we should try and get
Ban Perl hooks into regexes
=head1 ABSTRACT
Remove C?{ code }, C??{ code } and friends.
At first, I thought you were crazy, then I read
It would be preferable to keep the regular expression engine as
self-contained as possible, if nothing else to enable it to be used
either outside Perl
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Regex modifier for support of chunk processing and prefix matching
=head1 VERSION
Maintainer: Bart Lateur [EMAIL PROTECTED]
Date: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 316
Version:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Access to optimisation information for regular expressions
=head1 VERSION
Maintainer: Hugo van der Sanden ([EMAIL PROTECTED])
Date: 25 September 2000
Mailing List: [EMAIL PROTECTED]
Number: 317
Wouldn't this interact rather badly with the /gc option (which also leaves
Cpos set on failure)?
This question arose because I was trying to work out how one would write a
lexer with the new /z option, and it made my head ache ;-)
As you can see from the example code, the program flow
I agree with both of you. It would be nice if @$ precedence worked as Bart
specified, but I still think that arrays should be arrays.
The problem is that
$name = "myarray";
@$name = (1,2,3);
print @$name[0,1]; # 1,2
Is very consistent currently. Change one and you have to change
On Mon, Sep 25, 2000 at 02:56:20AM -0500, Curtis Jewell wrote:
Or would this tool be restricted to compile-time dependencies only?
I see no problem restricting dependency graphs to compile-time
dependencies.
Z.
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Replace localtime() and gmtime() with date() and utcdate()
=head1 VERSION
Maintainer: Nathan Wiger [EMAIL PROTECTED]
Date: 5 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Simple assignment lvalue subs should be on by default
=head1 VERSION
Maintainer: Nathan Wiger [EMAIL PROTECTED]
Date: 24 Aug 2000
Last-Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Transparently integrate Ctie
=head1 VERSION
Maintainer: Nathan Wiger [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 319
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Apache-like Event and Dispatch Handlers
=head1 VERSION
Maintainer: Nathan Wiger [EMAIL PROTECTED]
Date: 14 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 101
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Common Callback API for all AIO calls.
=head1 VERSION
Maintainer: Uri Guttman [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 321
Version: 1
Status: Developing
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
Nathan Wiger [EMAIL PROTECTED] writes:
package Doggie;
sub isborn {
bless { @_ }, self; # ;-)
}
sub scratches ($\@;@) {
...
}
package Doggie::Cute;
use base 'Doggie';
use interface 'Pet';
# Our base class
On Mon, Sep 25, 2000 at 06:02:51AM -, Perl6 RFC Librarian wrote:
=head1 ABSTRACT
File tests (-r/-w/-x/...) made sense when Perl's shellness was an
attribute. Most new Perl programmers are not coming from a shell
programming background, and the -X syntax is opaque and bizarre.
It
Adam Turoff wrote:
I plan to offer a more formal RFC of this idea.
=item perl6storm #0004
Need perl to spit out pod/non-pod, like cc -E. Pod is too hard to parse.
This would make catpod trivially implemented as a compiler filter.
Note that this functionality is trivial if RFC79 is
Nathan Wiger wrote:
In fact, I'd much rather still a more generic function like 'want' that
takes a list of things to check:
file($file, 'd'); # is it a directory?
file($file, 'wd'); # is it a writable directory?
if ( all { $_-($file) } \writable, \directory ) { ...
:-)
On Mon, Sep 25, 2000 at 01:55:10PM +0100, Richard Proctor wrote:
It does not seem to have much to do with tr///, if you want it, why not put it
in a module with some meaningful name such as histogram()?
Hm. Counting doesn't have much to do with tr///, if you think of it like that.
Now, if
On Mon, 25 Sep 2000 14:44:16 +0100, Simon Cozens wrote:
Incidentally, so what if a hash is slow? You pay for what you get. It's still
quicker than doing it by hand.
This is for the cases where epeople forget that they are "asking" for
it. I don't want comp.lang.perl.misc or any other support
On 25 Sep 2000 06:07:01 -0700, Randal L. Schwartz wrote:
Bart Plus, in Perl 5, NO core function returns a hash.
Bart None at all.
It's not returning a hash. I like the proposal that has it return a
paired list, similar to the semi-paired list we get with a capturing
split, or a list-context
=head1 TITLE
First-Class CGI Support
Perl6 should be *easier* to write CGI programs than Perl5. One way to
accomplish this is to add a C-cgi option to Perl, so that all of the
mechanical setup is done automatically. That setup could also be done
through a Cuse cgi; pragma.
To make
On 25 Sep 2000, Perl6 RFC Librarian wrote:
=head1 TITLE
Remove -X
The prefered mechanism for file tests should be more legible, using
terms like 'readable(FOO)' and 'writeable(FOO)' instead of the
=head1 MIGRATION ISSUES
Perl programmers happy with the -X syntax will need to get
Many mechanisms exist to make perl code and data persistant. They should
be cleaned up, unified, and documented widely within the core
documentation.
But doesn't this go against TMTOWTDI. :)
Different people might have different requirements. Portability would want
all ASCII, large apps
On Mon, Sep 25, 2000 at 03:30:47PM +0200, Bart Lateur wrote:
If you can garantee that it's also not using a hash internally to keep
count, but instead a table parallel to the table that's being used to
hold the conversion values, you've won me over.
Naturally, it's hard to guarantee anything
Simon,
I think I said in the RFC, didn't I? It's extending the counting use of tr///
to allow you to count several different letters at once. For instance, letter
frequencies in text is an important metric for linguists, codebreakers and
others; think about how you'd get letter frequency
David Grove wrote:
On Monday, September 25, 2000 9:16 AM, Chris Nandor [SMTP:[EMAIL PROTECTED]]
wrote:
Yes, but no one can restrict the redistribution of Perl (or perl). You
can, perhaps (though I am not entirely convinced), restrict the
distribution of some specific distribution, but
At 12:28 PM 9/25/00 -0400, Ben Tilly wrote:
As long as Larry is really OK with giving away the store, I don't think anyone
else should object.
"Giving away the store", such as it is (and it really isn't) is,
ultimately, good for perl, and something we should encourage.
The more ubiquitous Perl
Have you tried those avenues?
I have, and I received a confession of guilt in the process, I'm afraid, and an
"I don't care".
David Grove wrote:
Um, distribution under the GPL has to include offers of source.
In fact the terms of the GPL are all designed to promote a very
specific philosophy that is counter to traditional commercial
practices!
True, but it hasn't always happened.
People do not always meet
Is there anything that stops me from taking my binary copy
of Perl from ActiveState, cutting it to CD, and handing it to
someone else? I thought not!
You appear to be unfamiliar with ActiveState's license. It is specifically
prohibited from being redistributed without permission, from Perl
This is the nightmare of JavaScript. This is one of the reasons
that I prefer Perl over Java. This is...you know my opinion.
But I recognize the benefit as well. I don't think it is a
*bad* choice, but I think it is a choice to be made with open eyes
and recognition of the tradeoffs.
It proved a point. The point was, you said that there was no such thing, then
turned right around and gave it a name with the complete realization that the
problem exists, and where.
Again, this is a valid licensing concern, do not turn it into a pro- or con-
ActiveState rant. My intention in
On Mon, Sep 25, 2000 at 01:22:53PM -0400, Ben Tilly wrote:
The more ubiquitous Perl the language (as opposed to perl the
implementation) is, the better off we all are. I, for one, would be
*thrilled* if once we got a solid reference doc out for perl 6 someone else
besides us wrote an
David Grove wrote:
Is there anything that stops me from taking my binary copy
of Perl from ActiveState, cutting it to CD, and handing it to
someone else? I thought not!
You appear to be unfamiliar with ActiveState's license. It is specifically
prohibited from being redistributed without
On Mon, Sep 25, 2000 at 02:02:30PM -0400, Chris Nandor wrote:
No. I acknowledged that you perceive it as a problem, becacuse I've seen
you rant on it before, many times. I do not acknowledge any problem at all.
Might I humbly suggest that this discussion is going nowhere fast? Correction,
Simon Cozens wrote:
On Mon, Sep 25, 2000 at 01:22:53PM -0400, Ben Tilly wrote:
[...]
As soon as you get many implementations, you start to get into
the portability nightmare.
Not at all! That's what the solid reference doc's for. Evidently we
disagree
on how solid it should be. :)
On Monday, September 25, 2000 9:16 AM, Chris Nandor [SMTP:[EMAIL PROTECTED]]
wrote:
Yes, but no one can restrict the redistribution of Perl (or perl). You
can, perhaps (though I am not entirely convinced), restrict the
distribution of some specific distribution, but not perl (or Perl)
At 19:07 +0100 2000.09.25, Simon Cozens wrote:
On Mon, Sep 25, 2000 at 02:02:30PM -0400, Chris Nandor wrote:
No. I acknowledged that you perceive it as a problem, becacuse I've seen
you rant on it before, many times. I do not acknowledge any problem at all.
Might I humbly suggest that this
David Grove wrote:
On Monday, September 25, 2000 7:01 AM, Chris Nandor [SMTP:[EMAIL PROTECTED]]
wrote:
At 23:42 -0500 2000.09.24, David Grove wrote:
Whatever is done, it should be clear that a situation that exists today
should
not be permitted in the future. It should be impossible for
At 10:45 -0500 2000.09.25, David Grove wrote:
expensive on the market. This restriction of redistribution of the perl core
binary _is_ taking advantage of the situations and licenses unfairly and
There is no such restriction. Nowhere is the perl binary for any specific
platform restricted. On
At 11:28 -0500 2000.09.25, David Grove wrote:
You think my "company X" is ActiveState?
It always is.
Evidently you've recognized a problem
area that I may not have seen before
But you HAVE seen it before. You've specifically discussed this apparent
problem on many occassions. Please do not
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Cmy Dog $spot is just an assertion
=head1 VERSION
Maintainer: Piers Cawley [EMAIL PROTECTED]
Date: 13 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 218
Version: 2
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
PRAYER - what gets said when you Cbless something
=head1 VERSION
Maintainer: Simon Cozens [EMAIL PROTECTED]
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 307
Version: 1
Status:
RFC 189 covers this.
Damian
2000-09-25-12:04:44 Matt Youell:
Unless I hear compelling arguments to the contrary, I'll be
withdrawing RFC 161 on Tuesday due to lack of interest.
If the only grounds is lack of interest, please just freeze it. It
can be tossed later if people turn up strong counterarguments, like
This RFC proposes a special sub, CPRAYER, which is automatically called
on Cblessing.
Damian already covered this issue very thoroughly in RFC 189:
"Hierarchical calls to initializers and destructors".
-Nate
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Interface polymorphism considered lovely
=head1 VERSION
Maintainer: Piers Cawley [EMAIL PROTECTED]
Date: 20 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 265
RFC 207(v2) was posted several days ago with substantial changes from
v1. Since then, I have seen little (if any) discussion of the new or old
versions. As such, I am assuming that the RFC is acceptable as it
stands. As such, unless I hear otherwise before 28 September 2000, 5:00PM
New
At 01:22 PM 9/25/00 -0400, Ben Tilly wrote:
Dan Sugalski wrote:
The more ubiquitous Perl the language (as opposed to perl the
implementation) is, the better off we all are. I, for one, would be
*thrilled* if once we got a solid reference doc out for perl 6 someone else
besides us wrote an
Dan Sugalski wrote:
[...]
As soon as you get many implementations, you start to get into
the portability nightmare. We differ on how much of a problem
we think that is.
Multiple implementations are good. All the languages that've had long-term
viability have had multiple implementations.
At 03:57 PM 9/25/00 -0400, Ben Tilly wrote:
Dan Sugalski wrote:
[...]
As soon as you get many implementations, you start to get into
the portability nightmare. We differ on how much of a problem
we think that is.
Multiple implementations are good. All the languages that've had long-term
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 on
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
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 best speedup
On Mon, Sep 25, 2000 at 11:31:08PM +0100, Hugo wrote:
In [EMAIL PROTECTED], Perl6 RFC Librarian writes:
:=head1 ABSTRACT
:
:Remove C?{ code }, C??{ code } and friends.
Whoops, I missed this bit - what 'friends' do you mean?
Whatever even more bizarre extensions people will have suggested
On Mon, Sep 25, 2000 at 08:56:47PM +, Mark-Jason Dominus wrote:
I think the proposal that Joe McMahon and I are finishing up now will
make these obsolete anyway.
Good! The less I have to maintain the better...
--
Keep the number of passes in a compiler to a minimum.
-- D.
On Mon, Sep 25, 2000 at 04:55:18PM -0400, Michael Maraist wrote:
A lot of what is trying to happen in (?{..}) and friends is parsing.
That's not the problem that I'm trying to solve. The problem I'm trying
to solve is interdependence. Parsing is neither here nor there.
--
Intel engineering
On Mon, Sep 25, 2000 at 08:56:47PM +, Mark-Jason Dominus wrote:
I think the proposal that Joe McMahon and I are finishing up now will
make these obsolete anyway.
Good! The less I have to maintain the better...
Sorry, I meant that it would make (??...) and (?{...}) obsolete, not
that
In [EMAIL PROTECTED], Perl6 RFC Librarian writes:
:It would be preferable to keep the regular expression engine as
:self-contained as possible, if nothing else to enable it to be used
:either outside Perl or inside standalone translated Perl programs
:without a Perl runtime.
:
:To do this, we'll
Date: Sat, 23 Sep 2000 00:02:36 -0400
From: Wordsmith [EMAIL PROTECTED]
Subject: A.Word.A.Day--hyperbaton
To: [EMAIL PROTECTED]
hyperbaton (hye-PUR-buh-ton), noun, plural hyperbatons, hyperbata
The use, especially for emphasis, of a word order other than the
expected or usual one, as in
That is, the expression:
$check = ^_ == ^_**2 *^_ or die ^_;
Shouldn't that be
$check = (^_ == ^_**2 *^_ or die ^_);
due to precedence of = over "or"?
is equivalent to:
$check = sub (;) {
$_[0] == $_[1]**2 *$_[2] or die $_[3]
};
--
On Mon, 25 Sep 2000, Ben Tilly wrote:
Dan Sugalski wrote:
[...] I'm seriously thinking of instituting an "All
code
submitted to the repository belongs to Larry" rule until we have this
hashed out, so there's only one copyright holder to deal with.
We had that discussion. You would be
Something that I am a little stuck on...here is my understanding of the
way Perl is currently distributed and what it all means. I think I must
be confused about something...could someone straighten me out?
1) Works developed in Perl may be distributed under either the GPL or the
AL, dealer's
On Mon, 25 Sep 2000 10:19:05 +0100, Simon Cozens wrote:
(%alphabet) = $string =~ tr/a-z//;
Yum.
You want it in a hash? Ooff. Well, maybe that's ok for Perl6.
For Perl5, it would seem to make more sense, to me, to return a list.
Simply a matter of consistency with the spirit of the rest of
Perl6 RFC Librarian wrote:
=head1 ABSTRACT
Perl is frequently used in CGI environments. It should be as easy to write
CGI programs with perl as it is to write commandline text filters.
=head1 DESCRIPTION
Tom Christiansen proposed this in his perl6storm message:
=item
From: Bart Lateur [mailto:[EMAIL PROTECTED]]
On Mon, 25 Sep 2000 10:19:05 +0100, Simon Cozens wrote:
(%alphabet) = $string =~ tr/a-z//;
Yum.
You want it in a hash? Ooff. Well, maybe that's ok for Perl6.
For Perl5, it would seem to make more sense, to me, to return a list.
On Mon, 25 Sep 2000 13:00:58 +0200, Henrik Tougaard wrote:
Are the counts stuffed in the array in the order they appear in the
tr-string? or in ascii-order? or whatever?
In the same order as they are in the tr/// string, of course.
@freq{'a' .. 'z', '0' .. '9'} = tr/a-z0-9//;
That
1 - 100 of 161 matches
Mail list logo
