On Fri, Sep 15, 2000 at 03:11:47PM -0600, Nathan Torkington wrote:
> Perl6 RFC Librarian writes:
> > This RFC proposes two-stage autoloading: one stage may be registered
> > to act when the symbol is encountered at compile time, the other
> > when the subroutine is called. Autoloading on the seco
=head1 VERSION
Maintainer: Michael Schwern <[EMAIL PROTECTED]>
Date: 16 September 2000
Mailing List: perl6-language
Number: ?
Version: 1
Status: Developing (Last Call)
Reply-To: perl6-language @perl.org
This and other RFCs are available on the web at
http://dev.perl.org/r
On Sat, Sep 16, 2000 at 03:36:45AM -, Perl6 RFC Librarian wrote:
> Change the way $SIG{__WARN__} and $SIG{__DIE__} are used
I don't think this is enough to repair $SIG{__WARN__} and
$SIG{__DIE__}. I know some people out there have some very strong
feelings about these pseudo-signals. It may
On Sat, Sep 16, 2000 at 03:24:32AM -, Perl6 RFC Librarian wrote:
> Currently, trying to dynamically assign to unnamed classes is very
> difficult:
>
>$pkg::$var = $val; # error
>${pkg}::$var = $val; # nope
>${$pkg::$var} = $val; # you wish
>${${pkg}::$var} =
Nathan Torkington wrote:
> Actually, I think I'd like to see this extended. I'd like to be able
> to hook into the parser so that when it sees a function call:
>
> foo()
>
> I can have it call my subroutine.
>
> foo_handler( $token_stream )
>
> foo_handler can access the token stream that ma
> "MGS" == Michael G Schwern <[EMAIL PROTECTED]> writes:
MGS> On Sat, Sep 16, 2000 at 03:36:45AM -, Perl6 RFC Librarian wrote:
>> Change the way $SIG{__WARN__} and $SIG{__DIE__} are used
MGS> I don't think this is enough to repair $SIG{__WARN__} and
MGS> $SIG{__DIE__}. I know so
Richard Proctor wrote:
> > Maybe I'm being too simplistic, I don't use tabs anymore.
> >
>
> Yes you are, the problem comes with mixing editors - some use tabs for
> indented material some dont, some reduce files using tabs etc etc. [I move
> between too many editors]. Perl should DWIM. I thin
Certainly I could live with this set of suggestions. The complete set. Thanks
Richard and Michael for developing them.
Michael G Schwern wrote:
> I'd say:
>
> 1) << does what it does now mod RFC 111 (ie. you can put whitespace in the
>terminator, but it doesn't effect anything)
>
> 2) <<<
On Sat, Sep 16, 2000 at 03:20:23AM -, Perl6 RFC Librarian wrote:
> Perl used to use $pkg'var instead of the modern $pkg::var. This is still
> in Perl 5. It's gotta go.
Aside from "its old", is there any particular reason why $pkg'var
should go? The only reason I saw was that $hash{a'b} doesn
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Change the way $SIG{__WARN__} and $SIG{__DIE__} are used
=head1 VERSION
Maintainer: Chris Hostetter <[EMAIL PROTECTED]>
Date: 15 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 236
Version: 1
S
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
rindex and index should return true/false values
=head1 VERSION
Maintainer: Nathan Torkington <[EMAIL PROTECTED]>
Date: Sep 12 2000
Last Modified: Sep 15 2000
Mailing List: [EMAIL PROTECTED]
Numbe
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Short-circuiting built-in functions and user-defined subroutines
=head1 VERSION
Maintainer: Garrett Goebel <[EMAIL PROTECTED]>
Date: 6 Sep 2000
Last Modified: 15 Sep 2000
Mailing List: [EMAIL PROTEC
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Retire chop().
=head1 VERSION
Maintainer: Nathan Torkington <[EMAIL PROTECTED]>
Date: 5 Sep 2000
Last Modified: 15 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 195
Version: 2
Status: Froze
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Require explicit m on matches, even with ?? and // as delimiters.
=head1 VERSION
Maintainer: Nathan Torkington <[EMAIL PROTECTED]>
Date: August 20, 2000
Last Modified: 15 Sep 2000
Mailing List: [EMA
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Fix C<$pkg::$var> precedence issues with parsing of C<::>
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 14 Aug 2000
Last Modified: 15 Sep 2000
Mailing List: [EMAIL PROTECTED]
> I loathe the indirect object syntax.
Well that makes one of us! ;-)
> Easy. Put them in a subroutine:
>
> sub format1 { format $template1, @data };
> sub format2 { print STDERR format $template1, @data };
> # etc.
Gag! Cough! Ack! :-}
Not trying to be mean, but this
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Legacy Perl $pkg'var should die
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 08 Aug 2000
Last Modified: 15 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 71
Version:
> > prints the result to the current filehandle (in a void context).
>
> The last one I think needs to be able to work on any filehandle via
> indirect object syntax, namely:
>
>format $FILE "<<< [[[ [[",
> $title,
On Fri, Sep 15, 2000 at 11:25:31AM -0700, Steve Fink wrote:
> I agree. I'd like q/.../ to stick as close to giving me ... as possible.
> I can live with the current 'foo\\bar' having only one backslash in it,
> but I'd rather not have to worry about anything else. I'd vote for
> Glenn's allowing t
On Fri, 15 Sep 2000 11:25:31 -0700, Steve Fink wrote:
>Does it strike anyone else as odd that 'foo\\bar' eq 'foo\bar'?
It's an necessary evil. You need a way to escape the string delimiter,
so that it can be included in the string, for which the backslash is
used. Hence, you need to be a be to e
On Thu, 14 Sep 2000 21:06:24 -0700, Glenn Linderman wrote:
>However, let's look at it the other way. How about instead of trying to _extend_
>single quote semantics, that instead we find a way of _disabling_ double quote
>semantics? Let's say within double quotes that \D reverts to single-quote
On Fri, 15 Sep 2000 08:13:26 -0400 (EDT), Eric Roode wrote:
>The here-doc terminators all line up with the perl code.
>The generated program is nicely indented relative to the left margin.
My sentiments exaclty.
I think I would compare this to normal TV programmes (the code)
interruped by spec
On Thu, 14 Sep 2000 03:11:54 -0400, Michael G Schwern wrote:
>The current stumper, which involves problems 1, 2 and 3 is this:
>
> if( $is_fitting && $is_just ) {
>die Dulce et decorum est
> Pro patria mori.
>POEM
> }
>
>I propo
Simon Cozens wrote:
> sub interpolate {eval "\"@_\""}
>
> Never say "there is no way". There's *always* a way, and 99% of the time it
> doesn't need to go in core.
Yes. Well, actually if you carefully read the thread about RFC 111 in which I got
the inspired flash that interpolation of variable
I'm happy with this solution, it seems to address everyone's needs.
-Nate
Michael G Schwern wrote:
>
> I'd say:
>
> 1) << does what it does now mod RFC 111 (ie. you can put whitespace in the
>terminator, but it doesn't effect anything)
>
> 2) <<< does (e).
First off, nice proposal. :-) I haven't had a change to digest the
entire thing (although I did read it all), but I would like to add a few
things:
> returns the result as a single multi-line string (in a scalar context)
> returns the result as a list of single-line strings (in a
> I think such modules are a bad idea, because their functionality is
> typically restricted.
What, you mean like CGI.pm ?! :-)
> This is a benefit? Forcing multiple authors to use the same 'this' or
> 'self' name across modules is not the perl way
Well, from this logically follows that "forci
> The current ideas tend to converge around
While reading the current rfc199.2 version I imagined another way
to do this. Instead of adding a new escape, what if we could
fiddle with the looping condition?
Given a grep that works like so:
sub mygrep(&@){
local $inde
Chaim Frenkel writes:
> I would like to have an undef returned.
Ah, I see. You want subroutines to return undef if they're given it
for any of their arguments. That'd break the lazy programmer practice
of passing undef expecting it to become "" or 0. They don't have
warnings on, of course.
Na
=head1 TITLE
Short-circuiting built-in functions and user-defined subroutines
=head1 VERSION
Maintainer: Garrett Goebel <[EMAIL PROTECTED]>
Date: 15 Sep 2000
Version: 3
Mailing List: perl6-language
Number: 199
Status: Developing
=head1 ABSTRACT
Allow built-in functions and user de
My first preference is for overriding constant strings.
My second preference is to provide a user-defined quoting operator mechanism,
possibly as part of a user-defined operator mechanism.
My third preference is for a new operator.
I personally do not want to see q() screwed with.
Nat
On Fri, Sep 15, 2000 at 01:33:01PM -0700, Nathan Wiger wrote:
> Michael G Schwern wrote:
> >
> > perl6-internals is probably the wrong forum for this, it was just
> > convenient. I think Dan's got the right idea, distribute a Taint
> > module with Perl.
>
> I'm not sure what's happened on -inte
Perl6 RFC Librarian writes:
> This RFC proposes two-stage autoloading: one stage may be registered
> to act when the symbol is encountered at compile time, the other
> when the subroutine is called. Autoloading on the second stage does not
> I the subroutine, only I it.
You have a beautiful min
Michael G Schwern wrote:
>
> perl6-internals is probably the wrong forum for this, it was just
> convenient. I think Dan's got the right idea, distribute a Taint
> module with Perl.
I'm not sure what's happened on -internals, but early on in
perl6-language I suggested something similar, and Lar
On Fri, Sep 15, 2000 at 04:01:11PM -0400, Dan Sugalski wrote:
> >Anyhow, however these extra tainting functions are implemented is fine
> >(as long as they work). The simplest thing would be to just merge and
> >patch up Taint.pm and distribute it with perl6.
>
> Yup. I know Tom wanted an all-pe
On Fri 15 Sep, Michael G Schwern wrote:
> On Fri, Sep 15, 2000 at 06:38:37PM +0100, Richard Proctor wrote:
> > 1) << removes whitespace equivalent to the terminator (e) this is largely
> > backward complatible as many existing heredocs are unlikely to have white
> > space before the terminator.
>
At 03:43 PM 9/15/00 -0400, Michael G Schwern wrote:
>On Fri, Sep 15, 2000 at 02:00:04PM -0400, Adam Turoff wrote:
> > I'm kinda surfing the edge here. -T is definately an internals issue,
> > but $TAINT? taint()? is_tainted()?
> >
> > I'm not sure if they should be exposed into the language fro
On Fri, Sep 15, 2000 at 02:00:04PM -0400, Adam Turoff wrote:
> I'm kinda surfing the edge here. -T is definately an internals issue,
> but $TAINT? taint()? is_tainted()?
>
> I'm not sure if they should be exposed into the language from the
> internals, or if a superstudly taint.xs in stdlib i
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Replace AUTOLOAD by a more flexible mechanism
=head1 VERSION
Maintainer: Ilya Zakharevich <[EMAIL PROTECTED]>
Date: 15 September 2000
Mailing List: [EMAIL PROTECTED]
Number: 232
Version: 1
Statu
On Fri, Sep 15, 2000 at 06:38:37PM +0100, Richard Proctor wrote:
> 1) << removes whitespace equivalent to the terminator (e) this is largely
> backward complatible as many existing heredocs are unlikely to have white
> space before the terminator.
>
> 2) <<< removes whitespace equivalent to the s
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Replace C built-in with pragmatically-induced C function
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 15 September 2000
Mailing List: [EMAIL PROTECTED]
Number: 230
Version: 1
On Fri, 15 Sep 2000 12:01:55 -0400, Mark-Jason Dominus wrote:
>When you translate a script, the translator should translate things so
>that they have the same meanings as they did before. If it doesn't
>also translate eval, then your Perl 5 scripts will be using the Perl 6
>eval, which isn't wha
Nathan Wiger wrote:
>
> Andy Dougherty wrote:
> >
> > How do you turn it off? I want to keep a way to specify stuff without any
> > interpolation whatsoever. I see the usefulness of this sort of quoting,
> > but I also see the usefulness of being absolutely able to turn all
> > interpolation off
On Fri 15 Sep, Nathan Wiger wrote:
> Michael G Schwern wrote:
> > So indenting the terminator and indenting the text are linked. If you
> > do one, you want to do the other.
>
> As I and many others have said, that's not necessarily true. I like all
> my code to line up, braces, parens, and all.
Michael G Schwern wrote:
>
> See, I never understood this. If you're indenting the terminator, it
> implies you're also indenting the here-doc text. I mean, this doesn't
> make any sense:
>
> { { { {
> print < I don't know what their
> gripe is. A critic is
> simply someone paid to
>
Andy Dougherty wrote:
>
> How do you turn it off? I want to keep a way to specify stuff without any
> interpolation whatsoever. I see the usefulness of this sort of quoting,
> but I also see the usefulness of being absolutely able to turn all
> interpolation off.
Yes, I agree with this point, a
Since there were no objections to cleaning up the error messages on
unbalanced parens and braces, can we RFC that request?
-Ed
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information
> eval should stay eval.
Yes, and this is the way to do that.
When you translate a script, the translator should translate things so
that they have the same meanings as they did before. If it doesn't
also translate eval, then your Perl 5 scripts will be using the Perl 6
eval, which isn't wha
My question:
using IO::SOCKET, i need to connect to multiple server at once.
The server side works very well; it only waits for connections over a fixed IP,port.
How can i write the client-side?
Please help me!
Perl6 RFC Librarian wrote:
>
> =head1 TITLE
>
> Inline Comments for Perl.
Why was this posted again? I see no CHANGES section.
> An idea that produces a paired feeling would be to use one of the
> paired character pairs, as in "#<" and ">#".
#Oh Lord, What Have I Gotten Myself Into
On Fri, 15 Sep 2000, Bart Lateur wrote:
> On Thu, 14 Sep 2000 18:14:49 -0400, Mark-Jason Dominus wrote:
>
> >The perl 5 -> perl 6 translator should [recursively handle eval]
>
> Blech, no. eval should stay eval. People are responsible for generating
> Perl6 compatible code, if they construct
Hildo Biersma wrote:
>
> I think such modules are a bad idea, because their functionality is
> typically restricted.
Oh? Where do you get that idea?
> Altering the language to make that easier seems a
> bad idea to me.
On the contrary: altering *anything* about Perl to make
something easier
On 14 Sep 2000, at 14:18, Nathan Wiger wrote:
> Before you balk at #1 in favor of religious flexibility, please consider
> how unmaintainable Perl code would be if @ARGV, or $AUTOLOAD, or STDERR,
> or @INC, or chomp(), or split(), or any other widely-used variable or
> function was renameable. If
Graham Barr wrote:
>
> One of the benefits I was hoping to get from having a variable hold
> the invocant is the ability for the invocant to be undef if the sub
> was not called as a method.
Um, functions can return undef too, ya know. :-)
--
John Porter
On Fri, Sep 15, 2000 at 05:56:36AM -, Perl6 RFC Librarian wrote:
> $foo = 'def';
> $bar = 'ghi';
> $x = "abc$foo$bar";
> $y = 'abc$foo$bar';
>
> There is no way to turn obtain the value of $x from the value of $y.
> In other words, while $foo and $bar were interp
> Perl6 should allow scalars and arrays to be tagged such that they are
> interpolated in single quotish context.
How do you turn it off? I want to keep a way to specify stuff without any
interpolation whatsoever. I see the usefulness of this sort of quoting,
but I also see the usefulness of bei
Michael Schwern wrote:
>See, I never understood this. If you're indenting the terminator, it
>implies you're also indenting the here-doc text. I mean, this doesn't
>make any sense:
>
>{ { { {
>print gripe is. A critic is
>simply someone paid to
>render opinions
On 14 Sep 2000, at 21:06, Glenn Linderman wrote:
> I _like_ the conceptual idea, here. But I think we need a different kind of
> quoting, not extend single quote semantics. Single quote semantics are really,
> really, good for exact quoting. I'm sure you (since you mention VMS) find single
> q
On 15 Sep 2000, at 1:10, Perl6 RFC Librarian wrote:
> With this proposal, the scalar C<$filename> can be tagged to be interpolated
> by the C<\I...\E> pair and the double quotish context replaced by single
> quotish context resulting in the following:
Definitely with this change, you should incl
On Thu, Sep 14, 2000 at 08:10:54PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Objects: C pragma
>
> =head1 VERSION
>
> Maintainer: Damian Conway <[EMAIL PROTECTED]>
> Date: 14 September 2000
> Mail
On Thu, 14 Sep 2000 18:14:49 -0400, Mark-Jason Dominus wrote:
>The perl 5 -> perl 6 translator should replace calls to 'eval' with
>calls to 'perl5_eval', which will recursively call the 5->6 translator
>to translate the eval'ed string into perl 6, and will then eval the
>result.
Blech, no. eval
On Thu, Sep 14, 2000 at 03:36:10PM -0700, Nathan Wiger wrote:
> See, this is just too inflexible. The main complaint that I've heard has
> been "You can't have leading or trailing whitespace around your
> terminator". This is a very common error made by everyone, and *this* is
> where Perl should
Nathan Wiger wrote:
> >
> > and this may, indeed, be sufficient.
>
> Remember, this still won't solve the problem of a module whose functions
> can handle both OO and function-oriented calls - and yes, I have many
> that do this. :-)
I think such modules are a bad idea, because their functional
63 matches
Mail list logo
