On 27 Sep 2000 09:16:10 +0300, Ariel Scolnicov wrote:
>Another option is to stuff the long names into some namespace, and
>export them upon request (or maybe not export them, upon request).
Can you say "method"?
--
Bart.
At 11:53 PM 9/26/00 -0400, Uri Guttman wrote:
>now what bothers me is that all those calls are in section 3 and are no
>section 2 system calls. maybe it is faked with threads but i haven't
>found any support for that notion. if so, i wonder if we can actually
>use it and not collide with perl thre
At 02:25 PM 9/25/00 +0100, David Mitchell wrote:
>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... :-) ]
Revisiting
At 05:37 AM 9/27/00 +, Perl6 RFC Librarian wrote:
>Perl should adopt scheme-like symbols, both at the language level
>and at the internals level.
The explanation of this isn't that clear for me. (I have no scheme
experience at all)
It sounds like a sort of dynamically-created version of C's
At 05:33 AM 9/27/00 +, Perl6 RFC Librarian wrote:
>Perl should be embeddable, and we should make it easy for people to
>embed it by making the API as simple as possible.
I've some notes on this that I never got together for an RFC. What I was
thinking we would want would be routines to:
* C
Uri Guttman <[EMAIL PROTECTED]> writes:
> > "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
>
> >> I'll revise the RFC to add 'readable()', 'writable()', and such
> >> synonyms for -r and -w that are more like 'use english' and less like
> >> 'use English'.
>
>
> i have a mi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
POD and comments handling in perl
=head1 VERSION
Maintainer: Richard Foley <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 325
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Symbols, symbols everywhere
=head1 VERSION
Maintainer: Paolo Molaro <[EMAIL PROTECTED]>
Date: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 326
Version: 1
Status: Developing
=head1 ABSTRA
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl's embedding API should be simple
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 323
Version: 1
Status: Developing
=he
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Abstract Internals String Interaction
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 322
Version: 1
Status: Developing
=he
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Rename the C operator
=head1 VERSION
Maintainer: J. David Blackstone <[EMAIL PROTECTED]>
Date: 4 Aug 2000
Last Modified: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 19
Version: 2
Statu
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Extend AUTOLOAD functionality to AUTOGLOB
=head1 VERSION
Maintainer: David Cantrell <[EMAIL PROTECTED]>
Date: 26 Sept 2000
Mailing List: [EMAIL PROTECTED]
Number: 324
Version: 1
Status: Developi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
IO: Standardization of Perl IO Functions to use Indirect Objects
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 15 Sep 2000
Last Modified: 26 Sep 2000
Mailing List: [EMAIL PROTECT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Thread Programming Model
=head1 VERSION
Maintainer: Steven McDougall <[EMAIL PROTECTED]>
Date: 31 Aug 2000
Last Modified: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 185
Version: 3
Sta
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Lightweight Threads
=head1 VERSION
Maintainer: Steven McDougall <[EMAIL PROTECTED]>
Date: 30 Aug 2000
Last Modified: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 178
Version: 5
Status:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Everything in Perl becomes an object.
=head1 VERSION
Maintainer: Matt Youell <[EMAIL PROTECTED]>
Date: 25 Aug 2000
Last Modified: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 161
Version:
without requiring strict 'vars'
Reply-To: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Yet another lexical variable proposal: lexical variables made default
without requiring strict 'vars'
=head1 VERSION
Maintainer: J. David Black
On Mon, 25 Sep 2000 19:26:38 -0700, Nathan Wiger wrote:
>> 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
>
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Lexical variables made default
=head1 VERSION
Maintainer: J. David Blackstone <[EMAIL PROTECTED]>
Date: 1 Aug 2000
Last Modified: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 6
Version: 3
Paris Sinclair <[EMAIL PROTECTED]> writes:
> But as soon as a person labels me a minority, and implies that because I
> have been labeled such that I am a rioter, and that my opinions are
> based upon this label, then your choices are to filter me, or to listen
> to me protest.
Then perhaps you
i keep parsing the subject of this rfc as 'ban perl books'
:)
uri
--
Uri Guttman - [EMAIL PROTECTED] -- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page --- http://www.sysarch.com/cgi-bin/per
> "TH" == Tom Hughes <[EMAIL PROTECTED]> writes:
TH> Certainly I know Unixware used to fake it up by creating a new
TH> thread and doing sync IO in that thread, and I think Solaris did
TH> the same but that was a couple of years ago now so things might
TH> be better now.
solaris has
>Could you please start from the assumption that we're all interested in
>supporting the full Unicode space to the greatest degree possible? None
>of us are trying to force an ASCII-only alphabet on anyone (although some
>of us are interested in keeping ASCII-only operations fast and efficient
>s
Paris Sinclair <[EMAIL PROTECTED]> writes:
> kOn Tue, 26 Sep 2000, Bennett Todd wrote:
>> Someone wrote:
>>> What's the upper bound in a 16bit language? Or does that case just
>>> have to break? "Sorry, you're not European. Please be assimilated
>>> before using this tool. Resistance is futile."
Simon Cozens wrote:
>
> Looks great on scalars, but...
>
> @foo =~ shift; # @foo = $foo[0] ?
> @foo =~ unshift; # @foo = $foo[-1] ?
Yes, if you wanted to do something that twisted. :-) It probably makes
more sense to do something like these:
@array =~ reverse;
@vals =~ sort {
On Mon, Sep 25, 2000 at 08:15:08PM -, Perl6 RFC Librarian wrote:
> How's this different from, for instance, generalizing source filters?
> Well, that's how I first tried to implement them in Perl, but line
> disciplines actually give you far, far more control over the file
> handling; your pr
In message <[EMAIL PROTECTED]>
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> What'd be a larger win would be if we have async I/O built into the core
> I/O subsystem. That way we could queue up requests for blocks of data
> (whatever data we want, in this case bytecode) and have them fetche
Dan Sugalski <[EMAIL PROTECTED]> writes:
> The issues I was thinking of have come up mainly from the Freeciv lists,
> and concern ordering of substituted output and suchlike things. Does it
> handle the case where in english you see:
>error %s in file %s
> but in some other language the two
Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
> Do you mean local time now or local time for all time? The former is
> easy, the latter hard. Well, it's not hard for those places where the
> offset from UTC has remained (mostly) constant, but there are some
> places that have an offset from U
On Tue, Sep 26, 2000 at 05:54:25PM -0400, Dan Sugalski wrote:
> At 05:50 PM 9/26/00 -0400, Dan Sugalski wrote:
> >At 02:14 PM 9/26/00 -0700, Benjamin Stuhl wrote:
> >>But the point of an I/O discipline is to convert to/from
> >>UTF-8, perl's internal form. If you want to write a
> >>shift-JIS to b
On Mon, Sep 25, 2000 at 06:30:22PM -0400, Karl Glazebrook wrote:
> > Well, this shows that you entirely miss the problem of cryptocontexts.
> > Context is determined by the "environment" of the operation, not by
> > the operation. Context is propagated:
> >
> > the-left-hand-side-of-assignment
Now, some of you may have noticed that I've suddenly started writing one or
two little RFCs. Yes, this is really me, the same guy who was convinced that
Perl 6 was an exercise in how quick we could all go to hell in a handbasket.
I admit it. I was wrong.
What's caused this dramatic change of min
In <[EMAIL PROTECTED]>, Bart Lateur writes:
:On 25 Sep 2000 20:14:52 -, Perl6 RFC Librarian wrote:
:
:>Remove C, C and friends.
:
:I'm putting the finishing touches on an RFC to drop (?{...}) and replace
:it with something far more localized, hence cleaner: assertions, also in
:Perl code. That
In <005501c027eb$43bafe60$[EMAIL PROTECTED]>, "Michael Maraist" writes:
:As you said, we shouldn't encourage full-fledged execution (since core dumps
:are common).
Let's not redefine the language just because there are bugs to fix.
Surely it is better to concentrate first on fixing the bugs so th
On Tue, 26 Sep 2000, Dan Sugalski wrote:
> The issues I was thinking of have come up mainly from the Freeciv lists,
> and concern ordering of substituted output and suchlike things. Does it
> handle the case where in english you see:
>
>error %s in file %s
>
> but in some other language th
Uri Guttman wrote:
>
> not the best. would that be confused with a sub readable and a leading
> unary negation? in fact how does perl parse -r now vs - r()?
Yes it would, here's how Perl parses these right now:
perl -w -e '
sub r { local $\; print "&r(@_) : "; }
$\ = "\n";
print "-r" if -
At 02:04 PM 9/26/00 -0500, David Grove wrote:
> > 4) Someone writes a new version of piece X of perl, for example a better
> > optimizer or a backend that interfaces into a compiler's back end. (Like
> > GCC or Digital's GEM compiler backend) Perl *is* the whole point here.
>
>I'm not familiar wit
> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> I think perhaps that Uri was suggesting more a common letter prefix,
NW> such as:
NW> freadable($file);
NW> fwritable($file);
NW> fexecutable($file);
NW> Than a piece of bastardized Pythonesque syntax. ;-)
basically c
> "AT" == Adam Turoff <[EMAIL PROTECTED]> writes:
AT> On Tue, Sep 26, 2000 at 02:13:41PM -0400, Uri Guttman wrote:
>>
AT> But I wouldn't want that pragma to override any other aspect of the
AT> core library, such as async I/O.
agreed. but we can reconcile the name spaces then. or le
Simon Cozens wrote:
>
> Maybe you'd prefer this:
>
> defun Schwartzian func list mapcar lambda x car x sort mapcar
> lambda x cons x funcall func x list lambda x y < cdr x cdr y
What happened to the newlines?
Also, "no parens" is not the only alternative to having parens.
Other punctiation is
Simon Cozens wrote:
> (defun Schwartzian (func list)
> (mapcar
>(lambda (x) (car x))
>(sort
> (mapcar
> (lambda (x) (cons x (funcall func x)))
> list
> )
> (lambda (x y) (< (cdr x) (cdr y)))
> )
>)
> )
>
> Maybe you'd prefer this:
>
> defun Schwartzian
2000-09-26-05:18:57 Paris Sinclair:
> > (%alphabet) = $string =~ tr/a-z//;
>
> also a little more concise (and certainly more efficient...) than
>
> %alphabet = map { $_ => eval "\$string =~ tr/$_//" } (a..z);
However, compared to say
$hist[ord($_)]++ for split //, $string;
No, not for
use 'strict';
That is not a bareword. Hard to say why (have short time).
Only "$a = fred" is a bareword. But "require Module", is not,
as it has another meaning, and is accomodated in the grammar.
Likewise, a prototype of sub fn(*) is not a bareword when
you call fn(Whatever).
Yes, while still allowing an explicit A()->B(), of course.
I just meant that A->B means A::->B(), or, if you would, "A"->B().
But A()->B would not change in meaning.
--tom, posting blind(ly)
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is int
Yes, Phil, I mean things like abs() meaning abs($_) and
localtime() meaning localtime(time).
Actually, combined with the paren requirement thingie, it means
localtime(time()), and localtime
has to be written localtime(). These are two different suggestions,
though.
This is an attempt at sendin
Russ, you can use "perl -" to punch/paste into that window.
But "foo | perl" would not be affected as you would not
be running interactively. Essentially, only if there
are no arguments and stdin (and stdout) areatty would you
do that.
--tom, posting blind
Visit our website at http://www.ubswar
On 24 Sep 2000, Perl6 RFC Librarian wrote:
I still hope that it doesn't get as complicated as all this. I know
there are arguments out there for specifying integer size and signedness
but I can't imagine that adding this stuff is a good thing.
> Note that multiple types cannot be specified on th
On Mon, Sep 25, 2000 at 10:10:39PM -0400, Bryan C. Warnock wrote:
> Someone's been busy...
I'm not finished yet.
> > C just throws everything. None of the above happens.
> What does "just throws everything" mean?
Oops, yes. I claimed I was going to thrash out the exact semantics of no
unicode
On Tue, 26 Sep 2000, Nathan Wiger wrote:
> I think perhaps that Uri was suggesting more a common letter prefix,
> such as:
>
> freadable($file);
> fwritable($file);
> fexecutable($file);
>
> Than a piece of bastardized Pythonesque syntax. ;-)
Was that what the foo.bar("baz") syntax was
Adam Turoff wrote:
>
> That's a stone's throw awaty from:
>
> import english
> from english import filetest
>
> result = filetest.readable("/dev/null")
>
> I think the common prefix idea is a nonstarter. There must be a way
> to coming up with sensible names for all of
On Tue, Sep 26, 2000 at 02:06:47PM -0400, John Porter wrote:
> > Since when do parentheses make things less readable?
>
> Can you say "lisp"?
"lisp".
(defun Schwartzian (func list)
(mapcar
(lambda (x) (car x))
(sort
(mapcar
(lambda (x) (cons x (funcall func x)))
list
On Tuesday, September 26, 2000 12:54 PM, Dan Sugalski [SMTP:[EMAIL PROTECTED]]
wrote:
> At 07:08 AM 9/26/00 -0400, Ben Tilly wrote:
> >Dan Sugalski wrote:
> >>
> >>On Mon, 25 Sep 2000, Ben Tilly wrote:
> >>
> >> > Is it a conflict with the aims of Perl 6 in general that various
> >> > derivatives
On Tue, Sep 26, 2000 at 02:13:41PM -0400, Uri Guttman wrote:
>
> and if the file test names are only loaded via a pragma it should be
> ok. it is not clear to me that you want that.
It's not clear that I want that either.
This is probably a plea for a subset of 'use english;', possibly
'use en
> There is, but as MJD wrote: "it ain't pretty". Now, semantic checks or
> assertions would be the only reason why I'd expect to be able to execute
> perl code every time a part of a regex is succesfully parsed. Simply
> look at RFC 197: a syntactic extension to regexes just to check if a
> number
Dan Sugalski wrote:
>At 07:08 AM 9/26/00 -0400, Ben Tilly wrote:
>>Dan Sugalski wrote:
>>>
>>>On Mon, 25 Sep 2000, Ben Tilly wrote:
>>>
>>> > Is it a conflict with the aims of Perl 6 in general that various
>>> > derivatives of Perl should be licensed under the AL+GPL or GPL?
>>> > (ie Implementat
On Tue, 26 Sep 2000 13:32:37 -0400, Michael Maraist wrote:
>
>I can't believe that there currently isn't a means of killing a back-track
>based on perl-code. Looking through perlre it seems like you're right.
There is, but as MJD wrote: "it ain't pretty". Now, semantic checks or
assertions wou
On 25 Sep 2000, at 13:05, Ben Tilly wrote:
> David Grove wrote:
>
> > However, I am speaking in generalities. If it's
> > perl, it's redistributable. If it isn't redistributable, it isn't
> > perl. This include both binaries and source, since binaries are only
> > translations of source into anot
On 25 Sep 2000, at 10:03, Ben Tilly wrote:
> I think David is confused about this situation, but what he
> said is not entirely false. Anyone who wants can get Perl,
> make changes under the GPL, and release the hacked up version
> under the GPL. You would now have a GPL-only fork of Perl
> whi
Philip Newton wrote:
>
>On 25 Sep 2000, at 10:03, Ben Tilly wrote:
>
> > I think David is confused about this situation, but what he
> > said is not entirely false. Anyone who wants can get Perl,
> > make changes under the GPL, and release the hacked up version
> > under the GPL. You would now h
At 07:08 AM 9/26/00 -0400, Ben Tilly wrote:
>Dan Sugalski wrote:
>>
>>On Mon, 25 Sep 2000, Ben Tilly wrote:
>>
>> > Is it a conflict with the aims of Perl 6 in general that various
>> > derivatives of Perl should be licensed under the AL+GPL or GPL?
>> > (ie Implementations of Perl either are done
> I'm kind of curious to know what you think would happen with the
> following. I've commented where I'm confident...
>
> interface Number;
> sub TIESCALAR;
> sub STORE;
> sub FETCH;
>
> package integer implements Number; # I really like this notation
Tangentially, yes, it i
> On 25 Sep 2000 20:14:52 -, Perl6 RFC Librarian wrote:
>
> >Remove C, C and friends.
>
> I'm putting the finishing touches on an RFC to drop (?{...}) and replace
> it with something far more localized, hence cleaner: assertions, also in
> Perl code. That way,
>
> /(?
> would only match integ
On 25 Sep 2000 20:14:52 -, Perl6 RFC Librarian wrote:
>Remove C, C and friends.
I'm putting the finishing touches on an RFC to drop (?{...}) and replace
it with something far more localized, hence cleaner: assertions, also in
Perl code. That way,
/(?
Jonathan Scott Duff wrote:
>
> Or would C just use C and punt to the OS/C RTL/etc.?
Yes, I believe that would be the idea. Or something else exactly like it
;-). Resolving localtime is not our concern; presenting it in a
human-usable format is. And there's no reason you couldn't do this:
use
Not to sound too, a, whatever...
but you rock,
Get it started, make it available, and I will format it into a pleasant (interactive)
web page, I promise !!!
(thinking faq-omatic)
2000-09-26-08:10:54 Webmaster:
> Simon Cozens [EMAIL PROTECTED] Wrote:
> >Perl 6 needs some kind of internationalisation and therefore message
> >catalogue support. Really needs, with great urgency.
>
> Doesn't RFC 85 address this to some extent? By offering up 'error codes'
> can't the programme
> Somewhat to my own surprise, I really like this RFC.
Thanks :-)
> My only disagreement is that I think it's a mistake to defer the call
> to TIEWHATEVER until the first access. It ought to be done when
> the typed variable is declared, so that it's easy to determine where
> a variable is tied.
> VMS must die!
Hahahahaha !!!
On Tue, Sep 26, 2000 at 08:10:39AM -0700, Nathan Wiger wrote:
> And having a date() that returns local time, which will be most-used,
> is still a good thing, I think.
Do you mean local time now or local time for all time? The former is
easy, the latter hard. Well, it's not hard for those place
Jonathan Scott Duff wrote:
>
> I still think one of the options to the C routine could be the
> offset from UTC or a code ref to a subroutine that can determine the
> offset given the current UTC. That way the user could specify what
> localtime means (even if it doesn't really mean local time ;-
On Tue, Sep 26, 2000 at 05:49:38AM -, Nathan Wiger wrote:
> =head1 NOTES ON FREEZE
>
> Everyone felt pretty good about this, I think. The only thing we'd all
> probably like to see is one single C function, but unfortunately
> dealing with timezone specifications is an extraordinarily difficu
On Tue, Sep 26, 2000 at 05:53:13AM -, Nate Wiger wrote:
> Currently, file tests cannot be grouped, resulting in very long
> expressions when one wants to check to make sure some thing is a
> readable, writeable, executable directory:
>
>if ( -d $file && -r $file && -w $file && -x $file )
On Tue, Sep 26, 2000 at 12:34:00AM -0400, Adam Turoff wrote:
> Making '@permissions = -rwx $filename;' work is an interesting new
> suggestion.
Yep.
> Of course, I should say that I've been hanging out with some
> snake-hearders recently.
Hey, we could learn a thing or two from some snake her
On Tue, Sep 26, 2000 at 12:04:50AM -0400, Adam Turoff wrote:
> On Mon, Sep 25, 2000 at 07:50:28AM +0100, Richard Proctor wrote:
> > On Mon 25 Sep, Perl6 RFC Librarian wrote:
> > > Turn on tainting
> >
> > What would it do on a platform that does not support Tainting?
>
> Is this a real issue? I
Chris Nandor wrote:
>
>At 6:02 -0400 2000.09.26, Ben Tilly wrote:
> >Dave Storrs wrote:
> >>
> >>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 stra
On Tue, Sep 26, 2000 at 08:10:54AM -0400, Webmaster wrote:
> Simon Cozens [EMAIL PROTECTED] Wrote:
> >Perl 6 needs some kind of internationalisation and therefore message
> >catalogue support. Really needs, with great urgency.
>
> Doesn't RFC 85 address this to some extent?
Not really. Well, it
At 6:02 -0400 2000.09.26, Ben Tilly wrote:
>Dave Storrs wrote:
>>
>>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 deve
Simon Cozens [EMAIL PROTECTED] Wrote:
>Perl 6 needs some kind of internationalisation and therefore message
>catalogue support. Really needs, with great urgency.
Doesn't RFC 85 address this to some extent? By offering up 'error codes'
can't the programmer just "insert-test-here"? Then again, if 8
From: Damian Conway [mailto:[EMAIL PROTECTED]]
...
>
> No. That's my point. I want to match BANG followed by maximal whitespace
> followed by another BANG. But a line-by-line filter fails dismally if that
> maximal whitespace contains a newline.
>
> Admittedly this particular example is contrived
Dan Sugalski wrote:
>
>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 wi
On Sun, Sep 17, 2000 at 05:41:57AM -, Perl6 RFC Librarian wrote:
>. Some criticized it as being too sugary, since this:
>
>$string =~ quotemeta;# $string = quotemeta $string;
>
> Is not as clear as the original. However, there is fairly similar
> precedent in:
>
>$x += 5;
Dave Storrs wrote:
>
>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
Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Transparently integrate C
On the whole I think I'm liking this. But it needs work.
>my packed $a; # just an assertion, RFC 218
>$a
On Tue, Sep 26, 2000 at 09:49:44AM +0100, Piers Cawley wrote:
> Why am I having bad thoughts along the lines of:
>local @STACK = @SAVED_STACK
Because, Piers, you're sick. Keep up the good work.
--
"Jesus ate my mouse" or some similar banality.
-- Megahal (trained on asr), 1998-11-06
On Tue, Sep 26, 2000 at 04:41:21AM -0400, Alan Gutierrez wrote:
> > > > > Robust input parsing: yes.
> > > >
> > > > > General purpose output formatting: no, [...]
> > > >
> > > > > Rudimentary HTTP header emission: probably.
>
> So this is the definition of first-class?
Have you read the RFC
On Mon, 25 Sep 2000, Simon Cozens wrote:
> On Mon, Sep 25, 2000 at 09:55:38AM +0100, Richard Proctor wrote:
> > While this may be a fun thing to do - why? what is the application?
>
> I think I said in the RFC, didn't I? It's extending the counting use of tr///
> to allow you to count several d
Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
> 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
Simon Cozens <[EMAIL PROTECTED]> writes:
> On Tue, Sep 26, 2000 at 07:20:08AM +1100, Damian Conway wrote:
> > RFC 189 covers this.
>
> So it does! Cool, I can withdraw mine *and* get the warm fuzzy feeling that
> comes from like-thinking-of-great-minds.
>
> RFC 307 is withdrawn!
I do like the
Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> C<@STACK> - a modifyable C
Why am I having bad thoughts along the lines of:
local @STACK = @SAVED_STACK
I don't know what'd do, but it'd be f
On Tue, 26 Sep 2000, iain truskett wrote:
> * Adam Turoff ([EMAIL PROTECTED]) [26 Sep 2000 17:15]:
> > On Tue, Sep 26, 2000 at 05:02:02PM +1100, iain truskett wrote:
> > > Is there much point having a lightweight CGI module? If you say 'I want
> > > it to load quickly', I say 'get mod_perl'.
Agr
"David L. Nicol" wrote:
>
> > Perl currently only has C and C operators which work case-sensitively.
> > It would be a useful addition to add case-insensitive equivalents.
>
> As I recall, the consensus the last time this came up was that C and
> C would be perfect examples w/in a RFC proposing
On Tue, Sep 26, 2000 at 07:20:08AM +1100, Damian Conway wrote:
> RFC 189 covers this.
So it does! Cool, I can withdraw mine *and* get the warm fuzzy feeling that
comes from like-thinking-of-great-minds.
RFC 307 is withdrawn!
--
How do I type "for i in *.dvi do xdvi i done" in a GUI?
(Discussio
On 24 Sep 2000, Perl6 RFC Librarian wrote:
> Eliminate unquoted barewords from Perl entirely
Ugh, don't force me to select a One True Way, PLEASE. I don't think there
is really any unresolvable ambiguities the way it is in Perl5. Lets not
sacrifice the ability to do it the right way, just to pre
Somewhat to my own surprise, I really like this RFC.
My only disagreement is that I think it's a mistake to defer the call
to TIEWHATEVER until the first access. It ought to be done when
the typed variable is declared, so that it's easy to determine where
a variable is tied.
There is also the
CHAIR: Simon Cozens <[EMAIL PROTECTED]>
WORKING GROUP: perl6-internals-unicode
CHAIR: Simon Cozens <[EMAIL PROTECTED]>
DEADLINE: Oct 28, 2000
MISSION: Develop a consistent vision of how perl should
handle unicode (and all character data) internally.
DESCRIPTION: This group's mission is to get pe
95 matches
Mail list logo
