On Fri, Sep 29, 2000 at 09:58:45AM +0100, Hildo Biersma wrote:
=head1 ABSTRACT
Remove all interpolation within single quotes and the Cq() operator, to
make single quotes 100% shell-like. C\ rather than C\\ gives a single
backslash; use double quotes or Cq() if you need a single
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Advanced I/O (AIO)
=head1 VERSION
Maintainer: Uri Guttman [EMAIL PROTECTED]
Date: 29 Sept 2000
Mailing List: [EMAIL PROTECTED]
Number: 350
Version: 1
Status: Developing
=head1 ABSTRACT
This
you would do:
$sock = AIO::Open( Host = 'www.perl.org',
Port = 80 ) ;
Similarly for LWP you would just do:
$sock = AIO::Open( Url = 'http://www.perl.org' ) ;
$event = AIO::Open( Host = 'www.perl.org',
Port
Jonathan Scott Duff [EMAIL PROTECTED] writes:
On Thu, Sep 28, 2000 at 08:57:39PM -, Perl6 RFC Librarian wrote:
${P1} means what $1 currently means (first match in last regex)
I'm sorry that I don't have anything more constructive to say than
"ick", but ... Ick.
I'm with the 'Ick'
On Fri, 29 Sep 2000 01:02:40 +0100, Hugo wrote:
It also isn't clear what parts of the expression are interpolated at
compile time; what should the following leave in %foo?
%foo = ();
$bar = "one";
"twothree" =~ / (?$bar=two) (?$foo{$bar}=three) /x;
It's not just that. You act
In [EMAIL PROTECTED], "Richard Proctor" writes:
:In general all assignments should wait to the very end, and then assign
:them all. [...] If the expression finally fails the localised values
:would unroll.
Ah, I hadn't anticipated that - I had assumed you would get whatever
was the last value
On Fri, 29 Sep 2000 13:19:47 +0100, Hugo wrote:
I think that involves
rewriting your /p example something like:
if (/^$pat$/z) {
print "found a complete match";
} elsif (defined pos) {
print "found a prefix match";
} else {
print "not a match";
}
Except that this isn't
On Thu, 28 Sep 2000, Hugo wrote:
:=item *
:/(foo)_C\1_bar/
Please don't do this: write C/(foo)_\1_bar/ or /(foo)_\1_bar/, but
don't insert C in the middle: that makes it much more difficult to
read.
Sorry; that was a global-replace error that I missed on
proofreading.
:mean
On Fri, 29 Sep 2000, Hildo Biersma wrote:
Currently, C\1 and $1 have only slightly different meanings within a
regex. Let's consolidate them together, eliminate the differences, and
settle on $1 as the standard.
Sigh. That would remove functionality from the language.
The reason
In [EMAIL PROTECTED], Perl6 RFC Librarian writes:
:=item assertion in Perl5
:
: (?(?{not COND})(?!))
: (?(?{not do { COND }})(?!))
Or (?(?{COND})|(?!)).
Migration could consider replacing detectable equivalents of such
constructs with the favoured new construct.
:"local" inside embedded code
Simon Cozens [EMAIL PROTECTED] writes:
On Thu, Sep 28, 2000 at 02:40:04PM -0400, John Porter wrote:
Tom Christiansen wrote:
Perl's use of @ISA is beautiful.
use base is, or can be, pretty silly --
think pseudohashes, just for one.
I suppose you diddle @INC directly, Tom,
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Cuse syntax
[ ... ]
=head1 ABSTRACT
A pragma to modify the syntax of Perl 6 at run time. Oh yes.
[...]
=head1 IMPLEMENTATION
First,
It really is not feasible to relax the pod
requirement that pod diretives begin with
an equals to allow them to begin with a
pound sign as well, for to do so would expose
an untold number of programs to unpredictable
effects. I also don't really see any advantage.
And yes, I'm sure I'm days
On Fri, Sep 29, 2000 at 02:34:55AM +, Ed Mills wrote:
I tried to contribute on this list bu
--
"He was a modest, good-humored boy. It was Oxford that made him insufferable."
It is unreasonably complicated to do single-character
input in a portable fashion. We should therefore
include the Term::ReadKey module in the standard
distribution.
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the
On Fri, Sep 29, 2000 at 09:39:20AM +0100, Simon Cozens wrote:
On Fri, Sep 29, 2000 at 02:34:55AM +, Ed Mills wrote:
I tried to contribute on this list bu
[You know, I think something went wrong there. Let's try again.]
The RFC process gets you a hotline to Larry on an equal footing with
On 28 Sep 2000, Perl6 RFC Librarian wrote:
The Cheader function would work very similarly to CCGI.pm's:
@HEADERS = header(content_type = 'text/html',
author = 'Nathan Wiger',
last_modified = $date,
accept = [qw(text/html
I briefly considered
{
use syntax "python";
}
and nearly lost my lunch.
And if you want to lose your breakfast too, consider:
use "lisp";
use "apl";
(Although if the array-processing and currying RFCs are accepted, Perl will
finally have powers beyond those of
On 29 Sep 2000, Perl6 RFC Librarian wrote:
Make Perl's powerful string interpolation facilities are available to
variables, in addition to literals.
=head1 DESCRIPTION
Given:
$foo = 'def';
$bar = 'ghi';
$x = "abc$foo$bar";
$y = 'abc$foo$bar';
There is no way to turn obtain
Hm. This makes it difficult to construct a header incrementally -- for
example, @HEADERS=(); push @HEADERS, header(content_type='a',
author='b'); # 75 lines later; push @HEADERS, header(last_modified='c',
accept='d');
Since in this case, there would be two "blank" head lines instead of
I goofed. (EWRONGLIST)
I realise now that I should have said that RFC 328 (and 327) should have
been on this list, not perl-language-data
I had what I thought was a good look at previous RFCs but managed to miss
RFC226 (Selective interpolation in single quotish context.)
What I wanted comments
On Fri, 29 Sep 2000, Nathan Wiger wrote:
Should result in C@out being exactly equivalent to C@in.
It cannot, of course, since the order of hash keys obtained by flattening
the hash is not necessarily the same as when you built the hash.
Actually, it does. Remember, a hash is just a
=head1 TITLE
Common attribute system to allow user-defined, extensible attributes
Err... have you read perldoc attributes? There's already a mechanism
for doing this (see my japh), though it is a complete PITA to use and
I'd like to see it tidied up (and possibly have attributes.pm
Did anyone suggest the following yet?
package Foo;
my sub _helper_function { ... }
sub public_function {
...
helper_function(...);
...
}
# Some other file:
use Foo;
Foo::public_function(@args); # Okay
Foo::_helper_function(@args); #
On Fri, Sep 29, 2000 at 04:13:46PM +0100, Piers Cawley wrote:
Did anyone suggest the following yet?
package Foo;
my sub _helper_function { ... }
Todo:
lexically scoped functions: my sub foo { ... }
the basic concept is easy and sound,
the difficulties begin with
=head1 TITLE
Method calls should not suffer from the action on a distance
Currently,
foo-bar($baz)
can be parsed either as C'foo'-bar($baz), or as Cfoo()-bar($baz)
depending on how the symbol Cfoo was used on other places. The proposal
is to always choose the first meaning: make
"John L. Allen" wrote:
Um, what would your proposal gain you over
$z = eval "qq{$y}";
other than conciseness, elegance and speed (which may be quite enough!) ?
$y = '};system "rm -rf *";qq{';
--
Robert Mathews
Software Engineer
Excite@Home
Alan Gutierrez wrote:
HTML::Embperl stuffs form input into a hash just as proposed here. For
multiple values it creates a tab-delimited string. This will not present
the above trouble with commas, since when the user, for some odd reason,
enters "Ann Arbor\tMI", in most browsers the input
On Fri, 29 Sep 2000, Robert Mathews wrote:
"John L. Allen" wrote:
Um, what would your proposal gain you over
$z = eval "qq{$y}";
other than conciseness, elegance and speed (which may be quite enough!) ?
$y = '};system "rm -rf *";qq{';
Hmmm, hold on a second while I test
From: "Nathan Wiger" [EMAIL PROTECTED]
Sent: Friday, September 29, 2000 12:51 AM
James Mastros wrote:
As far as setting|getting, I'd like to make a simple proposal. Consider
it
an idea for whoever writes the RFC (I'm looking at you, Nate)
Oh, jeez, as if I didn't have enough already! ;-)
In a perl program I found the need to determine the command line swithches
passed to perl to be used to invoke the program. But I couldn't find
anything that gave this. There is $^X but that's limited.
I needed to reinvoke perl with all the -S and -I etc. commands.
(I needed a daemon that could
* Philip Newton ([EMAIL PROTECTED]) [30 Sep 2000 02:47]:
On 28 Sep 2000, at 21:36, iain truskett wrote:
[]
It's a case of: if you're going to have the output order, then you
should provide for the input to be ordered. *As well as* unordered.
Sorry, I don't follow your line of
On 29 Sep 2000, Piers Cawley wrote:
Is it possible? Advisable?
I haven't seen it yet, but that doesn't mean it's not in there
somewhere...there's a bunch of RFCs I haven't had time to read. If it
isn't there, it should be. I think this is definitely a cool idea.
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Single quotes don't interpolate \' and \\
=head1 VERSION
Maintainer: Nicholas Clark [EMAIL PROTECTED]
Date: 28 Sep 2000
Last Updated: 29 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 328
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 Modified: 29 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Provide a standard module to simplify the creation of source filters
=head1 VERSION
Maintainer: Damian Conway [EMAIL PROTECTED]
Date: 20 Sep 2000
Last Modified: 29 Sep 2000
Mailing List: [EMAIL
"David L. Nicol" wrote:
it's not a new feature. It's amazing the subtle control you
can get with s/(\$...)/$1/ge depending on your
You mean /gee, right? Hadn't thought of that. /ee makes my brain hurt.
--
Robert Mathews
Software Engineer
Excite@Home
=head1 ABSTRACT
Remove all interpolation within single quotes and the Cq() operator, to
make single quotes 100% shell-like. C\ rather than C\\ gives a single
backslash; use double quotes or Cq() if you need a single quote in your
string.
Yes. If people really need single quotes inside
On Fri, Sep 29, 2000 at 09:20:23PM -, Perl6 RFC Librarian wrote:
Although consensus so far is against the change, views were from Bexisting
perl users [who do you expect as the majority on perl6 lists? :-)]. The
change would penalise existing perl users, but benefit new perl users (and
On Fri, Sep 29, 2000 at 09:47:00PM -, Perl6 RFC Librarian wrote:
Classic eval:
eval {}
eval ""
Unscoped eval
+eval {}
+eval ""
I like the general idea of this RFC, but the proposed syntax is less than
desirable. What happens with the following?
$result = 20+eval"$x $op
Perl6 RFC Librarian wrote :
|| =head1 TITLE
||
|| Single quotes don't interpolate \' and \\
||
|| =head1 VERSION
||
|| Maintainer: Nicholas Clark [EMAIL PROTECTED]
|| Date: 28 Sep 2000
|| Last Updated: 29 Sep 2000
|| Mailing List: [EMAIL PROTECTED]
|| Number: 328
|| Version: 2
||
caller-eval EXPRESSION;
That's mad, bad, scary and dangerous. Let's do it.
Yes, this is cool. In fact, I'm writing Regexp::Func right now as a
prototype for RFC 164 and discovering I could really use this - in fact,
need it.
A couple things:
1. Implement this eval as
At 04:22 PM 9/29/00 -0700, Damien Neil wrote:
On Fri, Sep 29, 2000 at 09:20:23PM -, Perl6 RFC Librarian wrote:
Single quotes don't interpolate \' and \\
I rather like the Python triple-quote mechanism used for this
purpose:
$foo = """Things like ', ", and \ have no special meaning in
- -Original Message-
- From: Russ Allbery [mailto:[EMAIL PROTECTED]]
-
- Perl6 RFC Librarian [EMAIL PROTECTED] writes:
-
- However, lack of C\v represents a special case for a C programmer to
- learn. C\v isn't used for anything else in double quoted
- strings, nor
- is it used in
David Olbersen [EMAIL PROTECTED] writes:
From: Russ Allbery [mailto:[EMAIL PROTECTED]]
Just out of curiosity, and I'm not objecting to this RFC, has anyone
reading this mailing list actually intentionally used a vertical tab
for something related to its supposed purpose in the past ten
On 27 Sep 2000, Piers Cawley wrote:
Simon Cozens [EMAIL PROTECTED] writes:
On Wed, Sep 27, 2000 at 03:49:10PM +0100, Tom Christiansen wrote:
Don't change "use less" to "use optimize". We don't
need to ruin the cuteness.
"use less 'rolled_loops';" sounds really weird.
We
=head1 ABSTRACT
An unscoped eval is needed. It is part of the necessary steps to
make Perl palatable as an interactive shell.
I agree with Michael that the syntax is not suitable. If it's a separate
function, then it needs to be a \w+ name.
You should check out RFC 339 - it talks about a
* Nathan Wiger ([EMAIL PROTECTED]) [29 Sep 2000 02:14]:
A future protocol could well require things in order. Hence you're
having the output headers in order. Therefore you should have the
input ones available in order as well.
I don't see a reason why an @HTTP ordered and %HTTP unordered
On Fri, 29 Sep 2000, Robert Mathews wrote:
Alan Gutierrez wrote:
HTML::Embperl stuffs form input into a hash just as proposed here. For
multiple values it creates a tab-delimited string. This will not present
the above trouble with commas, since when the user, for some odd reason,
* Alan Gutierrez ([EMAIL PROTECTED]) [30 Sep 2000 14:47]:
[...]
Pity about Solaris. I wonder if Gerard Richter, HTML::Embperl mainter,
has ideas about this?
Does it really matter since it's a textarea? Typically you know which
fields are only going to have one value and can just not split the
On Sat, 30 Sep 2000, iain truskett wrote:
Or someone could split CGI.pm up so that there's CGI::FormValues and
CGI::HTTPHeaders.
By jove Mr. Truskett, that sounds like a smashing idea! Could we RFC
this? Do you think Mr. Stien would think us pushy?
IMHO this thread is discussing the
* Alan Gutierrez ([EMAIL PROTECTED]) [30 Sep 2000 14:55]:
On Sat, 30 Sep 2000, iain truskett wrote:
Or someone could split CGI.pm up so that there's CGI::FormValues and
CGI::HTTPHeaders.
By jove Mr. Truskett, that sounds like a smashing idea! Could we RFC
this? Do you think Mr. Stien
On 28 Sep 2000, Perl6 RFC Librarian wrote:
=head1 TITLE
Add Cheader and Cunheader funtions to core distribution
=head2 Location
These are such lightweight functions that their impact on core would be
negligible. As such, they could potentially be put directly into it,
since they are
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
caller-eval BLOCK
=head1 VERSION
Maintainer: David Nicol [EMAIL PROTECTED]
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 339
"Ed Mills" [EMAIL PROTECTED] writes:
I tried to contribute on this list but it seems we've coalesced downto Tom
and a handful of others. No one else has a voice.
Hmm... not my experience. But then I've only seen your message here
because of Simon's response to it, my spamfilter sees your
Piers Cawley [EMAIL PROTECTED] writes:
"Ed Mills" [EMAIL PROTECTED] writes:
I tried to contribute on this list but it seems we've coalesced downto Tom
and a handful of others. No one else has a voice.
Hmm... not my experience. But then I've only seen your message here
because of
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Common attribute system to allow user-defined, extensible attributes
=head1 VERSION
Maintainer: Nathan Wiger [EMAIL PROTECTED]
Date: 28 Sep
57 matches
Mail list logo
