Re: RFC 334 (v1) Perl should allow specially attributed subs to be called as C functions

At 04:13 PM 9/29/00 +0100, Nicholas Clark wrote: >Are you suggesting that the attributes use the same mapping system as >the XS (or son-of-XS (XS++)) typemaps in lib/ExtUtils/typemap? >If so, will there be the "terse" column in the typemap file to associate >"i" with "T_IV" ? Hadn't considered it

Re: RFC 125 (v2) Components in the Perl Core Should Have Well-Defined APIs and Behavior

At 04:17 PM 9/28/00 -0400, John Porter wrote: > > I think, though, that the core interface should be procedural. > >I agree. We should not confuse OOD with OOP. Fair enough, and I was. I've no experience with UML, though. Got a pointer to a quick overview?

Re: RFC 125 (v2) Components in the Perl Core Should HaveWell-Defined APIs and Behavior

Dan Sugalski wrote: > > At 04:17 PM 9/28/00 -0400, John Porter wrote: > > > I think, though, that the core interface should be procedural. > > > >I agree. We should not confuse OOD with OOP. > > Fair enough, and I was. > > I've no experience with UML, though. Got a pointer to a quick overview?

Re: RFC 343 (v1) New Perl Mascot

David Grove wrote: > > =head1 TITLE > > > > New Perl Mascot > > > > =head1 VERSION > > > > Maintainer: David Grove <[EMAIL PROTECTED]> > > Date: 28 Sep 2000 > > Mailing List: [EMAIL PROTECTED] > > Number: 343 > > Version: 1 > > Status: Developing > I hope you guys don't mind my placi

RE: RFC 343 (v1) New Perl Mascot

At 14:01 -0500 2000.09.29, Garrett Goebel wrote: >From: Tim Conrow [mailto:[EMAIL PROTECTED]] >> >> I don't know trademark law, but it seems unlikely that >> O'Reilly can trademark the concept of the camel, or all >> representations of the camel. > >No. They can't trademark the "concept" of the ca

Re: RFC 343 (v1) New Perl Mascot

Perl6 RFC Librarian wrote: > =head1 TITLE > > New Perl Mascot > > =head1 ABSTRACT > > Perl has no common symbol usable by the public at large to state to > the world "I am a Perl Programmer, and D**n Proud Of It!" > > =head1 DESCRIPTION > > The symbol that would be commonly used for this is t

Re: RFC 343 (v1) New Perl Mascot

Err.. A new version of a popular programming language? - Original Message - From: "Rocco Caputo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, September 29, 2000 8:20 PM Subject: RE: RFC 343 (v1) New Perl Mascot > On Thu, 28 Sep 2000 23:46:44 -0

RE: RFC 343 (v1) New Perl Mascot

From: Tim Conrow [mailto:[EMAIL PROTECTED]] > > I don't know trademark law, but it seems unlikely that > O'Reilly can trademark the concept of the camel, or all > representations of the camel. No. They can't trademark the "concept" of the camel. But they _have_ trademarked their camel logo and i

RE: RFC 343 (v1) New Perl Mascot

On Thu, 28 Sep 2000 23:46:44 -0500, David Grove wrote: [RFC 343 v1] A camel is a horse designed by committee. What do you get when you design a camel by committee? -- Rocco Caputo / [EMAIL PROTECTED]

Re: RFC 343 (v1) New Perl Mascot

Tim Conrow wrote: > I don't know trademark law, but it seems unlikely that O'Reilly can > trademark the concept of the camel, or all representations of the camel. I checked out the O'Reilly trademark at one point at the USA Trademark and Patent Office site. I don't have time to dig up the resul

RFC 347 (v1) Remove long-deprecated $* (aka $MULTILINE_MATCHING)

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Remove long-deprecated $* (aka $MULTILINE_MATCHING) =head1 VERSION Maintainer: Hugo van der Sanden <[EMAIL PROTECTED]> Date: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 347 Version: 1 St

RFC 348 (v1) Regex assertions in plain Perl code

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Regex assertions in plain Perl code =head1 VERSION Maintainer: Bart Lateur <[EMAIL PROTECTED]> Date: 28 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 348 Version: 1 Status: Developing =head1

Re: RFC 331 (v1) Consolidate the $1 and C<\1> notations

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. > >

Re: RFC 324 (v1) Extend AUTOLOAD functionality to AUTOGLOB

David Cantrell wrote: > > You can do it by explicitly calling your parent's AUTOGLOB as well if you're > asked to deal with something you don't support yourself (see below). Also, > having it as a single sub would be more easily extensible if we ever have > more datatypes (I think!) and results

Re: RFC 328 (v2) Single quotes don't interpolate \' and \\

> =head1 ABSTRACT > > Remove all interpolation within single quotes and the C operator, to > make single quotes 100% shell-like. C<\> rather than C<\\> gives a single > backslash; use double quotes or C if you need a single quote in your > string. Yes. If people really need single quotes inside

Re: RFC 328 (v2) Single quotes don't interpolate \' and \\

On Fri, Sep 29, 2000 at 09:20:23PM -, Perl6 RFC Librarian wrote: > Although consensus so far is against the change, views were from B > 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 > presuma

Re: RFC 351 (v1) Beyond the amnesic eval

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

Re: RFC 229 (v2) Variable interpolation on demand.

"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

Re: RFC 328 (v2) Single quotes don't interpolate \' and \\

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 ||

Re: RFC 339 (v1) caller->eval BLOCK

> > 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 UNIVERSA

RFC 351 (v1) Beyond the amnesic eval

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Beyond the amnesic eval =head1 VERSION Maintainer: Stéphane Payrard <[EMAIL PROTECTED]> Date: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 351 Version: 1 Status: Developing =head1 ABSTRA

Re: RFC 328 (v2) Single quotes don't interpolate \' and \\

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 here."""; Of course, this doesn't help if you wa

Re: RFC 328 (v2) Single quotes don't interpolate \' and \\

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 meani

Re: RFC 328 (v2) Single quotes don't interpolate \' and \\

On Fri, Sep 29, 2000 at 02:14:26PM -0800, Michael Fowler wrote: > On Fri, Sep 29, 2000 at 09:20:23PM -, Perl6 RFC Librarian wrote: > > Although consensus so far is against the change, views were from B > > perl users [who do you expect as the majority on perl6 lists? :-)]. The > > change would

Re: RFC 327 (v2) C<\v> for Vertical Tab

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 regular expressions, so it won't require removal of an > existing feature to add it.

Re: RFC 229 (v2) Variable interpolation on demand.

Robert Mathews wrote: > > "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. I actually usually do things like unde

Re: RFC 316 (v1) Regex modifier for support of chunk processing and prefix matching

In <[EMAIL PROTECTED]>, Bart Lateur writes: :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 {

Re: RFC 348 (v1) Regex assertions in plain Perl code

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

Re: RFC 352 (v1) Merge Perl and C#, but have default Main class for scripting.

On Fri, Sep 29, 2000 at 09:47:51PM -, Perl6 RFC Librarian wrote: > I am a fan of Perl and like what I see of the core C# _language_. > What I propose is to move Perl in the C# direction. So, this is the comedy RFC, eh? -- DEC diagnostics would run on a dead whale. -- Mel Fer

Issues of (6c) in Artistic-2.0 (was Re: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0))

From Artistic-2.0beta3 > > (4) You may modify your copy of the source code of this Package in any way > > and distribute that Modified Version (either gratis or for a > > Distribution Fee, and with or without a corresponding binary, bytecode > > or object code version of the M

Why (7) and (8) in the Artistic-2.0 (was Re: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0))

> > (7) You may aggregate this Package (either the Standard Version or > > Modified Version) with other packages and distribute the resulting > > aggregation provided that You do not charge a licensing fee for the > > Package. Distribution Fees are permitted, and licensing fee

Changes from 2.0beta2 to 2.0beta3

> The Artistic License > Version 2.0beta3, October 2000 I just realized that some of you might have read 2.0beta2 and don't want to take the time to read beta3. Here's the change, so you can view them quickly. I'll do the same for future ver

Re: RFC 343 (v1) New Perl Mascot

> New Perl Mascot > > Maintainer: David Grove <[EMAIL PROTECTED]> > Date: 28 Sep 2000 > Mailing List: [EMAIL PROTECTED] > Number: 343 > Version: 1 > Status: Developing I basically agree that we need a mascot, and one that isn't encumbered by a proprietary trademark license. Howeve

RE: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0)

YES. This is starting to make better sense and provide for some protections. Comments inserted. > Permissions for Redistribution of Modified Versions of the Package as Source > > (4) You may modify your copy of the source code of this Package in any way > and distribute that Modified Ve

RE: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0)

> >(b) ensure that the installation of Your non-source Modified Version > >does not conflict in any way with an installation of the > >Standard > >Version, and include for each program installed by the Modified > >Version clear documentation

RE: RFC 343 (v1) New Perl Mascot

Wait, is this a logic puzzle? A camel is designed by a committee, and is a horse what is a camel designed by committee? Answer is simple... a camel. it's actually a horse designed by committee unless I missed something Is this like the old question, if a rooster was sitting on a roof and lai

Re: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0)

David Grove wrote: > > >(b) ensure that the installation of Your non-source Modified Version > > >does not conflict in any way with an installation of the > > >Standard > > >Version, and include for each program installed by the Modified > > >

RE: RFC 265 (v3) Interface polymorphism considered lovely

> Java is one language that springs to mind that uses interface > polymorphism. Don't let this put you off -- if we must steal something > from Java let's steal something good. Interface inheritance is probably the least dignified thing to steal from Java. If we have true multiple inheritance, i

Re: RFC 319 (v1) Transparently integrate C

On 26 Sep 2000, Perl6 RFC Librarian wrote: > So, for example: > >package var; # main variable class > ># all the main Perl internal methods are defined, such ># as TIESCALAR, TIEARRAY, STORE, FETCH, etc > >package int; >use base 'var'; > ># ideas for RFC 303 >

Re: RFC 319 (v1) Transparently integrate C

Alan Gutierrez wrote: > > The suggested C< use optimize > pragma is starting to grow many heads. > C< use less > was such a simple little pragma, a general direction for > the interpreter to take. Here it seems that the optimizations apply to > the C< package int; > only. Are we suggesting that o

Re: RFC 352 (v1) Merge Perl and C#, but have default Main class for scripting.

Simon Cozens wrote: > > On Fri, Sep 29, 2000 at 09:47:51PM -, Perl6 RFC Librarian wrote: > > I am a fan of Perl and like what I see of the core C# _language_. > > What I propose is to move Perl in the C# direction. > > So, this is the comedy RFC, eh? Indeed. Since you quoted a couple of m

RE: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0)

On Friday, September 29, 2000 9:31 PM, Bradley M. Kuhn [SMTP:[EMAIL PROTECTED]] wrote: > David Grove wrote: > > > >(b) ensure that the installation of Your non-source Modified > > > >Version > > > >does not conflict in any way with an installation of the > > > >

RE: Why (7) and (8) in the Artistic-2.0 (was Re: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0))

> > Let ActiveState make their PerlScript, PerlEX, and pseudocompiler if they > > want, and charge whatever they want for it. But if perl is to be free, it > > needs to be redistributable without any loopholes providing them the > > ability to proprietarize the language itself, or make a community

Re: RFC 330 (v1) Global dynamic variables should remain the default

Nathan Wiger <[EMAIL PROTECTED]> writes: > Another proposal suggests that users should be forced to declare all > variables with C explicitly. Blech. That doesn't make anything > easy. Perl is not a B&D language. Actually Perl *can* be a Bondage & Discipline language but it's unique among such l

Re: RFC 331 (v1) Consolidate the $1 and C<\1> notations

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 'I

Re: RFC 335 (v1) Class Methods Introspection: what methods does this object support?

Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > This and other RFCs are available on the web at > http://dev.perl.org/rfc/ > > =head1 TITLE > > Class Methods Introspection: what methods does this object support? > > =head1 VERSION > > Maintainer: Mark Summerfield <[EMAIL PROTECTED]> >

Re: RFC 254 (v1) Class Collections: Provide the ability tooverload classes

On Thu, 28 Sep 2000, David L. Nicol wrote: [snip] >sub speak { print "kerokero"; } > >foreach (?) { # go through all the methods defined in Frog::Frog > # I know there is a way to do this but do not know what it is See RFC 335 (v1): Class Methods Introspecti

Re: RFC 120 (v5) Implicit counter in for statements, possibly $#.

Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > 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 >

Re: RFC 333 (v1) Add C and C funtions to coredistribution

On 28 Sep 2000, Perl6 RFC Librarian wrote: > The C function would work very similarly to C's: > >@HEADERS = header(content_type => 'text/html', > author => 'Nathan Wiger', > last_modified => $date, > accept => [qw(text/html text/

Re: RFC 316 (v1) Regex modifier for support of chunk processing and prefix matching

On Fri, 29 Sep 2000 00:29:31 +0100, Hugo wrote: >:I originally had thought of providing a separate, dedicated regex >:modifier, just for the match prefix, but I don't think too many people >:need this that desperately. You can easily build a working application >:with just the '/z' modifier. I

Re: RFC 336 (v1) use strict 'objects': a new pragma for using Java-like objects in Perl

Hi all Preamble: 1) Everybody: excuse my english, my italian is better but you don't want me to write in italian :-) 2) Listmaster: excuse this post from an unknown address, I've just subscribed as [EMAIL PROTECTED]; 3) Everybody again: excuse the address @perlguru.com, but I didn't want my work

Re: RFC 330 (v1) Global dynamic variables should remain the default

Piers Cawley wrote: > > Nathan Wiger <[EMAIL PROTECTED]> writes: > > > Another proposal suggests that users should be forced to declare all > > variables with C explicitly. Blech. That doesn't make anything > > easy. Perl is not a B&D language. > > Actually Perl *can* be a Bondage & Discipline

Re: A tentative list of vtable functions

At 02:29 PM 9/29/00 +0100, David Mitchell wrote: >Regarding the tentative list of vtable functions: >I'm rather worried about binary operators, eg 'is_equal', 'add' etc. >The danger with these is that they may impose a single implementation >of scalars upon us. > >As an example, suppose I wrote an

Re: RFC 229 (v2) Variable interpolation on demand.

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

Re: RFC 331 (v1) Consolidate the $1 and C<\1> notations

On Thu, 28 Sep 2000, Hugo wrote: > :=item * > :/(foo)_C<\1>_bar/ > > Please don't do this: write C 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 dif

Re: RFC 335 (v1) Class Methods Introspection: what methods does this object support?

Piers Cawley <[EMAIL PROTECTED]> writes: > Actually, I'd like to see something similar done to Universal::can my @methods = $class->can(pattern) where pattern is a perl pattern matching method names. For a full list, use $class->can(); or $class->can(qr/./); -- Johan

RFC 16 (v3) Keep default Perl free of constraints such as warnings and strict.

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Keep default Perl free of constraints such as warnings and strict. =head1 VERSION Maintainer: Daniel Chetlin <[EMAIL PROTECTED]> Date: 3 Aug 2000 Last Modified: 28 Sep 2000 Mailing List: [EMAIL PROT

RFC 163 (v3) Objects: Autoaccessors for object data structures

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Objects: Autoaccessors for object data structures =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 25 Aug 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 1

RFC 174 (v3) Improved parsing and flexibility of indirect object syntax

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Improved parsing and flexibility of indirect object syntax =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 29 Aug 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED

RFC 200 (v3) Objects: Revamp tie to support extensibility (Massive tie changes)

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Objects: Revamp tie to support extensibility (Massive tie changes) =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 7 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTEC

RFC 265 (v3) Interface polymorphism considered lovely

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: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 265 Vers

RFC 327 (v2) C<\v> for Vertical Tab

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE C<\v> for Vertical Tab =head1 VERSION Maintainer: Nicholas Clark <[EMAIL PROTECTED]> Date: 26 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 327 Version: 2 Status:

RFC 328 (v2) Single quotes don't interpolate \' and \\

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 Ve

RFC 333 (v2) Add C and C funtions to core distribution

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Add C and C funtions to core distribution =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 27 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 333

RFC 335 (v2) Class Methods Introspection: what methods does this object support?

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Class Methods Introspection: what methods does this object support? =head1 VERSION Maintainer: Mark Summerfield <[EMAIL PROTECTED]> Date: 28 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL

RFC 259 (v1) Builtins : Make use of hashref context for garrulous builtins

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

RFC 264 (v3) Provide a standard module to simplify the creation of source filters

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 PR

RFC 271 (v3) Subroutines : Pre- and post- handlers for subroutines

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: 20 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Numb

RFC 211 (v2) The Artistic License Must Be Changed

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE The Artistic License Must Be Changed =head1 VERSION Maintainer: Bradley M. Kuhn <[EMAIL PROTECTED]> Date: 12 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 211 Versi

RFC 219 (v2) Perl6's License Should Be a Minor Bugfix of Perl5's License

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Perl6's License Should Be a Minor Bugfix of Perl5's License =head1 VERSION Maintainer: Bradley M. Kuhn <[EMAIL PROTECTED]> Date: 13 Sep 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED

RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0)

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Perl6's License Should be (GPL|Artistic-2.0) =head1 VERSION Maintainer: Bradley M. Kuhn <[EMAIL PROTECTED]> Date: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 346 Version: 1 Status: Devel

RFC 349 (v1) Perl modules should be built with a Perl make program

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Perl modules should be built with a Perl make program =head1 VERSION Maintainer: Mark Leighton Fisher <[EMAIL PROTECTED]> Date: 29 Sept 2000 Mailing List: [EMAIL PROTECTED] Number: 349 Version: 1

RFC 350 (v1) Advanced I/O (AIO)

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

Re: RFC 350 (v1) Advanced I/O (AIO)

> 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', >

RFC 97 (v2) prototype-based method overloading

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE prototype-based method overloading =head1 VERSION Maintainer: David Nicol <[EMAIL PROTECTED]> Date: 13 Aug 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 97 Version: 2

RFC 98 (v3) context-based method overloading

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE context-based method overloading =head1 VERSION Maintainer: David Nicol <[EMAIL PROTECTED]> Date: 15 Aug 2000 Last Modified: 29 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 98 Version: 3 S

RE: RFC 352 (v1) Merge Perl and C#, but have default Main class for scripting.

On Friday, September 29, 2000 4:48 PM, Perl6 RFC Librarian [SMTP:[EMAIL PROTECTED]] wrote: > This and other RFCs are available on the web at > http://dev.perl.org/rfc/ > > =head1 TITLE > > Merge Perl and C#, but have default Main class for scripting. > > =head1 VERSION > > Maintainer: Timothy

RE: RFC 349 (v1) Perl modules should be built with a Perl make program

On Friday, September 29, 2000 4:45 PM, Perl6 RFC Librarian [SMTP:[EMAIL PROTECTED]] wrote: > This and other RFCs are available on the web at > http://dev.perl.org/rfc/ > > =head1 TITLE > > Perl modules should be built with a Perl make program > > =head1 VERSION > > Maintainer: Mark Leighton F

RE: Issues of (6c) in Artistic-2.0 (was Re: RFC 346 (v1) Perl6's License Should be (GPL|Artistic-2.0))

>(c) ensure that the Modified Version includes notification of the >changes made from the Standard Version, and offer the >machine-readable source of the Modified Version, under the exact >license of the Standard Version, by mail order. I feel a "in exc

Re: RFC 332 (v1) Regex: Make /$/ equivalent to /\z/ under the '/s' modifier

In <[EMAIL PROTECTED]>, Nathan Wiger writes: :> Is $$ the only alternative, or did I miss more? I don't think I've even :> seen this $$ mentioned before? : :$$ is not a suitable alternative. It already means the current process :ID. It really cannot be messed with. And ${$} is identical to $$ by :

Re: RFC 112 (v3) Asignment within a regex

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 as if

Re: RFC 331 (v1) Consolidate the $1 and C<\1> notations

> =head1 ABSTRACT > > 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 why you need \1 in a regu

Re: RFC 112 (v3) Asignment within a regex

> 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

Re: RFC 328 (v1) Single quotes don't interpolate \' and \\

> =head1 ABSTRACT > > Remove all interpolation within single quotes and the C operator, to > make single quotes 100% shell-like. C<\> rather than C<\\> gives a single > backslash; use double quotes or C if you need a single quote in your > string. Single-quoted strings need to be able to conta

Re: RFC 328 (v1) Single quotes don't interpolate \' and \\

On Thu, Sep 28, 2000 at 05:48:25PM -0500, David L. Nicol wrote: > > I don't like it, and here's why: > > > currently single quoted here docs don't interpolate C<\\> or C<\'>. > > > We already have a way to read in arbitrary literals. I _like_ the > fact that C allows backslash to be used to a

Re: RFC 328 (v1) Single quotes don't interpolate \' and \\

On Fri, Sep 29, 2000 at 09:58:45AM +0100, Hildo Biersma wrote: > > > =head1 ABSTRACT > > > > Remove all interpolation within single quotes and the C operator, to > > make single quotes 100% shell-like. C<\> rather than C<\\> gives a single > > backslash; use double quotes or C if you need a sin

RE: RFC 329 (v1) C

>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 tho

Re: A tentative list of vtable functions

Regarding the tentative list of vtable functions: I'm rather worried about binary operators, eg 'is_equal', 'add' etc. The danger with these is that they may impose a single implementation of scalars upon us. As an example, suppose I wrote an alternative scalar implementation that was optimised f

Re: RFC 334 (v1) Perl should allow specially attributed subs to be called as C functions

On Thu, Sep 28, 2000 at 08:59:58PM -, Perl6 RFC Librarian wrote: > =head1 DESCRIPTION > > Any sub that has the appropriate attribute can be called from C (or some other > compiled language). Perl will automagically convert the input > parameters (which is what the attributes tells us) to thin

Re: RFC 337 (v1) Common attribute system to allow user-defined, extensible attributes

> > =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 attribut

IDEA: lexically scoped subs anyone

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); # Th

Re: IDEA: lexically scoped subs anyone

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

Re: RFC 288 (v2) First-Class CGI Support

On 28 Sep 2000, at 21:36, iain truskett wrote: > * Philip Newton ([EMAIL PROTECTED]) [28 Sep 2000 21:19]: > > On 27 Sep 2000, at 23:48, iain truskett wrote: > > > > So surely you'd want %HTTP (the input headers) to also be an array > > > rather than a hash, since they'd be required in order as w

Re: RFC 229 (v2) Variable interpolation on demand.

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 tu

goof - RFC 328 (v1) Single quotes don't interpolate \' and \\

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 a

Re: RFC 333 (v1) Add C and C funtions to coredistribution

> 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 inste

Re: RFC 333 (v1) Add C and C funtions to coredistribution

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 h

Re: RFC 316 (v1) Regex modifier for support of chunk processing and prefix matching

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

Why -> cannot autoquote the LHS (was Re: RFC 244 (v1) Method calls should not suffer...)

> =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 C> > depending on how the symbol C was used on other places. The proposal > is to always choose the first meani

Re: RFC 229 (v2) Variable interpolation on demand.

"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

  1   2   >