> I think, if you look in the archives and the Camel, you'll find that turns
> out not to be the case.
I really don't like putting words in other people's mouths, so I'll
refrain. However, I have read comments from Larry and others in Camel
and perl5-porters that say something akin to this:
1
John Tobey <[EMAIL PROTECTED]> writes:
> On Wed, Aug 09, 2000 at 02:22:22AM +0200, Bart Lateur wrote:
>> date() would be more general, and replace both. You can pass it a time
>> zone, ANY time zone, and it will tell you what time it is in that time
>> zone.
You're proposing embedding the full p
>=head1 TITLE
>
>Higher order functions
Well, this should keep the Obfuscated Perl Contest going for at least
another decade :-)
--
Peter Scott
Pacific Systems Design Technologies
On Wed, 9 Aug 2000, Ken Fox wrote:
> Dan Sugalski wrote:
> > The number of different vtables needed to deal with this (along with
> > the functions in those tables) is rather formidable, and it will tend
> > to impact performance.
>
> Hey! That sounds like an implementation topic... ;) (The inte
Dan Sugalski wrote:
> The number of different vtables needed to deal with this (along with
> the functions in those tables) is rather formidable, and it will tend
> to impact performance.
Hey! That sounds like an implementation topic... ;) (The internals
should be able to handle this if the langu
> Higher order functions
This is a very nice proposal and I'd like to see it adopted. Since
many other RFCs are bound to assume this functionality, can we put
this one on the "fast track" approval process? ;)
- Ken
> "MP" == Matthew Persico <[EMAIL PROTECTED]> writes:
>> there are 2 ways i know how to do it now and both suck in different
>> ways. the first is to read the pod from the source file for the module
>> you are in. it think the pod2XXX parser author has a module which does
>> this. of
On Tue, Aug 08, 2000 at 10:59:40PM -0400, Dan Sugalski wrote:
> On Wed, 9 Aug 2000, Damian Conway wrote:
>
> >> > If you take this, I won't be able to port the forthcoming Klingon.pm
> >> > module to Perl 6!!!
> >>
> >> And this would be a bad thing how, exactly? :)
> >
> > I SH
Michael Fowler wrote:
> I would argue that you should be manipulating your data, or checking values,
> so that numbers and strings are sorted how you wish. The proposed isnum(),
> or way-to-determine-if-a-scalar-is-a-number would help. This should be an
> explicit check, though, because you have
On Tue, 8 Aug 2000, Mike Pastore wrote:
> On Tue, 8 Aug 2000, Dan Sugalski wrote:
> >
> > If you feel the need, it should be possible to let you do this, or at
> > least a part of it for one or three ops, with a module. I think it might
> > be better to wait until the plain way's in and then embe
On Wed, Aug 09, 2000 at 02:22:22AM +0200, Bart Lateur wrote:
> I have a server in the UK, while I'm in Belgium. Different time zones.
> So localtime() won't return the time in *my* localtime.
>
> So we have two almost identical functions in the core, gmtime and
> localtime, where one gives an off
On Tue, 8 Aug 2000, Dan Sugalski wrote:
>
> If you feel the need, it should be possible to let you do this, or at
> least a part of it for one or three ops, with a module. I think it might
> be better to wait until the plain way's in and then embellish it later.
I do believe (and please, folks, c
On Wed, 9 Aug 2000, Damian Conway wrote:
>> > If you take this, I won't be able to port the forthcoming Klingon.pm
>> > module to Perl 6!!!
>>
>> And this would be a bad thing how, exactly? :)
>
> I SHOULD KILL YOU WHERE YOU STAND
But, but... I'm sitting! :-P
On 9 Aug 2000, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> All Perl core functions should return objects
While an interesting idea, it'll mean we have a half-bazillion different
types of objects floating around just from the core. The number of
different vtables needed to deal with this (alon
> > If you take this, I won't be able to port the forthcoming Klingon.pm
> > module to Perl 6!!!
>
> And this would be a bad thing how, exactly? :)
I SHOULD KILL YOU WHERE YOU STAND
;-)
Damian
On Wed, 9 Aug 2000, Damian Conway wrote:
>> Perl used to use $pkg'var instead of the modern $pkg::var. This is still
>> in Perl 5. It's gotta go. (At least, it should.)
>
>
> N!
>
> If you take this, I won't be able to port the forthcoming Klingon.pm
> module to Perl 6!!!
And
On Tue, Aug 08, 2000 at 07:01:29PM -0700, Nathan Wiger wrote:
> > On Tue, Aug 08, 2000 at 02:18:07PM -, Perl6 RFC Librarian wrote:
> > > Hooks will have to be put in Perl's string context so that if something
> > > is an object, then that object's C method is called
> > > automatically. If no
> Perl used to use $pkg'var instead of the modern $pkg::var. This is still
> in Perl 5. It's gotta go. (At least, it should.)
N!
If you take this, I won't be able to port the forthcoming Klingon.pm
module to Perl 6!!!
;-)
Damian
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Higher order functions
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 4 August 2000
Version: 2
Mailing List: [EMAIL PROTECTED]
Number: 23
=head1 ABSTRACT
This RFC proposes so
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Proposal to rename C and C
=head1 VERSION
Maintainer: Jonthan Scott Duff <[EMAIL PROTECTED]>
Date: 8 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 74
=head1 ABSTRACT
C and C should
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
All Perl core functions should return objects
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 08 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Status: Developing
Nu
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
The regexp engine should go backward as well as forward.
=head1 VERSION
Maintainer: Peter Heslin <[EMAIL PROTECTED]>
Date: 9 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 72
=head1
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
Version: 1
Mailing List: [EMAIL PROTECTED]
Status: Developing
Number: 71
=hea
On Tue, 8 Aug 2000, Nathan Wiger wrote:
> However, as you point out, there's no easy way to get the HASH(addr)
> part. If this RFC is accepted, we might need a special function for that
> (but I say stick it in Data::Dumper).
Please don't worry about this. It's diving too deeply into what at thi
> On Tue, Aug 08, 2000 at 02:18:07PM -, Perl6 RFC Librarian wrote:
> > Hooks will have to be put in Perl's string context so that if something
> > is an object, then that object's C method is called
> > automatically. If no C method is defined, then it should simply
> > return undef (instead o
Ken Fox wrote:
> John Porter wrote:
> > Jeremy Howard wrote:
> > > Yes, they're not identical. What I mean of course is:
> > > (..-1) == reverse(map -__ (1..));
> >
> > WHAT? So the semantics of .. are magically different in the context
> > of (..$n) so as to produce numbers in descending order
* Perl6 RFC Librarian ([EMAIL PROTECTED]) [09 Aug 2000 05:44]:
> =head1 ABSTRACT
> Documents change, and change bars are a nice way to indicate what's
> changed. This RFC suggests a way to indicate the changed parts of a
> document that POD2whatever translators can mark appropriately. The
> chang
On Tue, 08 Aug 2000, Casey R. Tweten wrote:
> Today around 6:55pm, Bryan C. Warnock hammered out this masterpiece:
>
> : chop, chomp, (champ, chimp, chump, chap, and chip, which, respectively,
> : deletes all leading and trailing whitespace characters, all leading
> : whitespace characters, all t
On Tue, 08 Aug 2000, Brad hughes wrote:
> > Why not? Throw and catch are familiar to programmers.
>
> Not all programmers.
>
Oops, correct. My mistake. Even more reason not to introduce yet
another lexicon.
--
Bryan C. Warnock
([EMAIL PROTECTED])
John Porter wrote:
> Jeremy Howard wrote:
> > Yes, they're not identical. What I mean of course is:
> > (..-1) == reverse(map -__ (1..));
>
> WHAT? So the semantics of .. are magically different in the context
> of (..$n) so as to produce numbers in descending order?
Both of those expressions
* William Setzer ([EMAIL PROTECTED]) [09 Aug 2000 00:27]:
> iain truskett <[EMAIL PROTECTED]> writes:
[...]
> > If so, why? (Possibly cite the code.)
> Because it's more aesthetic (and useful) for me to see:
> open '/afs/bp.ncsu.edu/path/to/no_such_file': No such file or directory
> NCSU/Som
On Tue, 8 Aug 2000, Michael Mathews wrote:
> Ted Ashton said:
> > Thus it was written in the epistle of Uri Guttman,
> > >
> > > how do you tell the above two apart? by array do you mean only an array
> > > variable? then you can't chomp a list of scalar values or multiple
> > > arrays, etc.
> >
Uri Guttman wrote:
>
> here's an interesting request. i want perl code to have decent access to
> some or all of the pod associated with that code.
>
> so, why do we need a way to get at pod (or other doc strings) in the
> code? one reason to have it comes from my work on stem. i want a remote
>
"Bryan C. Warnock" wrote:
> On Tue, 08 Aug 2000, Peter Bevan wrote:
[...]
> > Error handling should be supported by it's own keyword
> i.e.: >
> > trap {
> > #CODE
> > }
> > release (error) {
> > # ERROR
> > }
> >
> > (just because I didn't want to steal throw and catch)
>
> Why not? Throw
I don't like the distinction between "anonymous" and other blocks.
On Tue, 8 Aug 2000 17:44:56 +0100, Graham Barr wrote:
>How usable is this ?
>
>I may be missing something, but if every variable mentioned in an anonymous
>block is assumed to be declared with my, then how do you access or modify
On Tue, 8 Aug 2000, Michael Mathews wrote:
> Dan Sugalski said:
> > > > * Do we even want to allow after-the-fact chomps, or do it
> automagically
> > >at read time?
> > "Yes" is rather ambiguous.
>
> To clarify: "Yes", we (I) want to allow after-the-fact chomps. As you
> alluded to yourself the
Peter Scott wrote:
> Have often wanted a way to tell whether a scalar was a number
> way to get at the SvIOK and SvNOK results would be great.
SvIOK, SvNOK and "is a number" are not the same thing at all.
Often numbers are strings that just look like numbers. Perl doesn't
eagerly convert stuff i
On Tue, 8 Aug 2000 18:35:46 -0400, Michael Mathews wrote:
>I frequently use chomp in ways that have nothing to do with "reading from
>files" and I would bet this is true for everyone here too. For example:
>
>use CGI;
>$cgi = new CGI;
>$foo = $cgi->param('foo');
>
>#as part of doing stuff to the
I like this approach, in that it places the complexity outside of the loop.
Another generalized approach might be a new $ var which turns autochomp off
and on for all fh's (are there any $'s left? :D ).
Cheers,
Ed
>From: Jonathan Scott Duff <[EMAIL PROTECTED]>
>To: Ed Mills <[EMAIL PROTECTED
On Tue, 8 Aug 2000 11:51:36 -0700, Damien Neil wrote:
>> The idea would
>> be localtime would be GONE in Perl 6, instead moved to Time::Local.
>> date() would replace it.
>
>Why is this a good idea? Perl programs have been using localtime() for
>over a decade. Why do we suddenly want to make th
> > Do you mean the whole thing, or just the `blocks' part?
>
> Any feature which subverts "use strict" by attempting to declare my
> variables for me. In this case -- `blocks'. But also `subs' scope,
> since that makes anonymous subs useless.
As the RFC notes:
=head2 Incompatibility with s
Today around 6:55pm, Bryan C. Warnock hammered out this masterpiece:
: chop, chomp, (champ, chimp, chump, chap, and chip, which, respectively,
: deletes all leading and trailing whitespace characters, all leading
: whitespace characters, all trailing whitespace characters, the first
: and last ch
> while($x)
> {
> $y += foo($x);
> $x = bar($x);
> $big_global_variable = analyze($y,$x);
> }
>
> This leaves you with three variables that may or may not be dependent
> on the upper scope for resolution by default.
As the RFC is written, only *anonymous* blocks are auto-
Today around 6:34pm, Mike Pastore hammered out this masterpiece:
: Perl++
PERL
[Casey ducks and runs for cover ;]
--
print(join(' ', qw(Casey R. Tweten)));my $sig={mail=>'[EMAIL PROTECTED]',site=>
'http://home.kiski.net/~crt'};print "\n",'.'x(length($sig->{site})+6),"\n";
print map{$_.': '.$
On 07 Aug 2000 13:57:14 +0200, Jean-Louis Leroy wrote:
>Bart Lateur <[EMAIL PROTECTED]> writes:
>
>> The problem is that you can't safely subclass a class, without examining
>> it's source, just to make sure that your instance fields don't clash
>> with any private fields of the mother class.
>
>
Thus it was written in the epistle of Peter Scott,
>
> I do not want a language designed by a committee, or even a
> democracy. This is art, not politics.
Preach on, brother!
Ted
--
Ted Ashton ([EMAIL PROTECTED]), Info Sys, Southern Adventist University
At 06:45 PM 8/8/00 -0400, Bryan C. Warnock wrote:
>I think that Perl survived its first through fifth births because the
>idioms it chose to implement were familiar.
>
>One could conceivably create a semantically pure language with
>no platform or OS dependencies, but then no one would use it.
>
>
Perl++
:)
On Tue, 8 Aug 2000, Bryan C. Warnock wrote:
> On Tue, 08 Aug 2000, Bennett Todd wrote:
>
> > If perl6 substantially fails to fill the important roles that perl5
> > fills, we should stop screwing everybody up by calling it "perl",
> > and call it something else.
>
> Hmmm. I vote fo
On Tue, 08 Aug 2000, Bennett Todd wrote:
> If perl6 substantially fails to fill the important roles that perl5
> fills, we should stop screwing everybody up by calling it "perl",
> and call it something else.
Hmmm. I vote for "Edsel."
--
Bryan C. Warnock
([EMAIL PROTECTED])
On Tue, 08 Aug 2000, Nathan Wiger wrote:
> There's two ways I see it:
>
> 1) do {} block
>
>$val = do {
> $x = 10;
> # ... stuff happens ...
> $y;
>};
>
> In which case $val = $y.
>
> 2) explicit our() scoping
>
>$x = 10;
>our $y = 10;
>{
> $
On Tue, 08 Aug 2000, Ed Mills wrote:
> As long as were culling, might want to consider removing chomp() and
> possibly chop(). The language provides other ways to accomplish those thru a
> simple regex,
Then we should remove regexs instead. :-)
> and if the "println" suggestion I made was "t
> I'm all for adding a new and improved time mechanism with a bit less
> of the oddness localtime() carries, but does it really hurt us to leave
> the old style in the core?
Not necessarily. But I think most people agree we should decide on one
interface. If we stuck to this, we'd have to move lo
On Tue, 08 Aug 2000, Peter Bevan wrote:
> However, with the birth of the new Perl, I think it is time to bury those
> ideoms in the language and
> start inventing new ones..
>
Two words: "New Coke"
I think that Perl survived its first through fifth births because the
idioms it chose to implemen
On Tue, 08 Aug 2000, Roman M . Parparov wrote:
> This is a tough one. But it is known that the numerical game scores and
> likewise are being written RTL. As for math, I've seen it being written
> both ways. I am not a native hebrew speaker and I consulted some natives
> at work and no consensus w
Bart Lateur said:
> So what are these really good for? To get rid of the line terminator, or
> "Record Separator", when reading from a file. That is what they are for,
> that is what we should facilitate. Not the chop()ping or chomp()ing of
> just any string.
>
> So, let's keep in tune with the R
Merge it in with the macro capability.
That would be an immediate subroutine. One that simply returns
undef. (i.e. Nothing inserted into the parse stream.)
Hmm, maybe nothing needs to be added to that.
> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes:
NT> I'm chewing over an RFC on
At 06:10 PM 8/8/00 -0400, Uri Guttman wrote:
>wacko idea:
>
>combine a generic data tree traverse engine with damian's switch op.
>
>you pass this new smart traverse a ref and it will scan the tree. at
>every node it sees, it can call callbacks or methods. it can do the
>callbacks in pre, in or p
Michael Mathews wrote:
>
> Like "join" the order of arguments would have to be "chomp($thing_to_remove,
> @array)" but this spoils the default behavior of $thing_to_remove being
> optional...
>
> unless you think we should require arrays to be passed by reference.
Well, if we were really talkin
Ted Ashton said:
> Thus it was written in the epistle of Uri Guttman,
> >
> > how do you tell the above two apart? by array do you mean only an array
> > variable? then you can't chomp a list of scalar values or multiple
> > arrays, etc.
> >
> > this needs to be clarified.
>
> Quite true. The two
wacko idea:
combine a generic data tree traverse engine with damian's switch op.
you pass this new smart traverse a ref and it will scan the tree. at
every node it sees, it can call callbacks or methods. it can do the
callbacks in pre, in or post ordering to get useful effects. if a node
is an
At 05:36 PM 8/8/00 -0400, Uri Guttman wrote:
>but why reinvent the wheel with this code? we have modules which do
>close to this now, and we have talked about using the GC traverse engine
>as well.
Yes, the code is only indirectly useful to the RFC since I expect it to be
implemented internally
At 04:17 PM 8/8/00 -0500, Garrett Goebel wrote:
>Here's a version of my own kludgey deep copy. -Updated to use our mythical
>->CLONE method, and watch for circular references...
Great stuff, I've put it in v2.
>[snip]
>: /^CODE$/ ? $_[0]# " (B::Deparse)
>[snip]
>I would like deep copyi
> "GG" == Garrett Goebel <[EMAIL PROTECTED]> writes:
GG> Oops, my circular ref code is/was screwy...
>> and $SEEN{$_} = $rval
>> or $SEEN = ();
that last line looks screwy too! :-) assigning an empty list to a scalar? i
think you meant to assign to %SEEN.
but why reinvent the wheel
> "JP" == John Porter <[EMAIL PROTECTED]> writes:
JP> Matt Sergeant wrote:
>>
>> I don't want to see Perl6 be so
>> fundamentally different to perl5 that I have to translate every single
>> script. I want some better stuff, but a new language is not what I'm
>> looking for.
JP
Oops, my circular ref code is/was screwy...
> --$DEPTH
> and $SEEN{$_} = ref($rval)
> or $SEEN = ();
should be
> --$DEPTH
> and $SEEN{$_} = $rval
> or $SEEN = ();
On Tue, Aug 08, 2000 at 09:50:27PM +0100, Matt Sergeant wrote:
> All I can say to that is, ugh! I don't want to see Perl6 be so
> fundamentally different to perl5 that I have to translate every single
> script. I want some better stuff, but a new language is not what I'm
> looking for.
All of you
Jonathan Scott Duff wrote:
>
> And what about user-defined contexts? (my Dog $spot = some_func();)
> I think a context coercion operator would do just fine.
Oh, I agree entirely! But the intrinsic contexts should have concise
operators (e.g. scalar()).
--
John Porter
Matt Sergeant wrote:
>
> I don't want to see Perl6 be so
> fundamentally different to perl5 that I have to translate every single
> script. I want some better stuff, but a new language is not what I'm
> looking for.
Well, I guess we all want something a little different.
I, for example, want a
On Tue, Aug 08, 2000 at 05:15:24PM -0400, John Porter wrote:
> Jonathan Scott Duff wrote:
> >
> > If we had a context coercion operator that was the opposite of want()
> > we could do something like this:
> >
> > print context '*STRING', $val; # long-hand for print $val
> > print contex
Ariel Scolnicov wrote:
>
> I rarely use a `now' scope,
Well, 'now' is a declaration; the scope is "temporal", aka "dynamic".
> Variable declaration is good (except for some trivial programs)!
I agree 1000%!
--
John Porter
Here's a version of my own kludgey deep copy. -Updated to use our mythical
->CLONE method, and watch for circular references...
our %SEEN = ();
our $DEPTH = 0;
%a = (a => 1, b => 2, c => [{a => 1, b => [1,2,3]}, 1, 2, 3]);
*b = dcopy(\%a);
sub dcopy { # Dereference and return a deep copy of wha
Jonathan Scott Duff wrote:
>
> If we had a context coercion operator that was the opposite of want()
> we could do something like this:
>
> print context '*STRING', $val; # long-hand for print $val
> print context '*SCALAR', $val; # we're not in a string context
> print conte
On Tue, Aug 08, 2000 at 12:17:12PM -0800, Michael Fowler wrote:
> So, some method should be provided to avoid the stringification, akin to
> overload::StrVal(). Perhaps overload::StrVal is sufficient.
If we had a context coercion operator that was the opposite of want()
we could do something lik
On Tue, 8 Aug 2000, Nathan Wiger wrote:
> > While I think Time::Object is a really great module, and following these
> > discussions I'm thinking of adding a date() function to it
>
> Aaah! Please don't. :-) Name it something else, por favor (or at least
> wait until this is finalized and make t
Nathan Wiger <[EMAIL PROTECTED]> writes:
[...]
> > I, for one, will *never* use such a construct. It provides the user
> > with the dangers of `no strict' combined with the illusion of safety
> > of `use strict'.
>
> Do you mean the whole thing, or just the `blocks' part?
Any feature which su
On Tue, 8 Aug 2000, Bart Lateur wrote:
> All you'd have to do, is set a boolean flag on the "filehandle object",
> saying: "Oi, I want this chomped.". For example:
>
> $fh->chomped(1);
>
> Then, what <$fh> would do, is read one line, looking for whatever line
> end it accepts, finish wher
Ugh, I'm being foolish. Let me clarify.
map { s/\r\n/ } @chomp_me;
would do the trick, for lists of things that need to be chomped. Perhaps
just a modification to the map function is needed, to support things like:
for(map { s/\r\n/ } $fh) {
print;
}
or maybe bind chomp to a new prototype
how does this work with RFC 63 (Exception handling syntax proposal - it
wants the Error.pm syntax) written by peter scott? you should look at
that and work with peter on this. and we are already discussing that rfc
in flow so please followup there only.
thanx,
uri
--
Uri Guttman - [
On Tue, 8 Aug 2000 10:12:49 -0700 (PDT), Larry Wall wrote:
>If chomp exists in Perl 6 at all, I think it would
>have to be some kind of method call on the string that figures out what
>the discipline determined to be the terminator *for the current line*.
>(Note that under Unicode, we might well
> fluid-let should *really* be called `now'),
Agreed (about the `now' part)
> Will this also apply to `use scope 'subs''?
No. Only subs are affected, which is a clear and easy dividing line I
believe.
> I, for one, will *never* use such a construct. It provides the user
> with the dangers of
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Allow exception-based error-reporting.
=head1 VERSION
Maintainer: Bennett Todd <[EMAIL PROTECTED]>
Date: 8 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 70
=head1 ABSTRACT
Allow fu
> =head1 TITLE
>
> Deep Copying, aka, cloning around.
> The C is an optional function to be called if C
> encounters a filehandle.
...or anything else it doesn't know how to handle.
> If C encounters a tied variable, it will call the C
> method...
...of the underlyin
On Tue, 8 Aug 2000, Ted Ashton wrote:
>
> Quite true. The two-argument one is new to me and I hadn't thought much
> about it. Do you have a suggestion?
Hmm,
chomp { /\r\n/ } @chomp_me;
ala p5 map, grep, and sort?
--
Mike Pastore
[EMAIL PROTECTED]
On Tue, Aug 08, 2000 at 02:18:07PM -, Perl6 RFC Librarian wrote:
> Hooks will have to be put in Perl's string context so that if something
> is an object, then that object's C method is called
> automatically. If no C method is defined, then it should simply
> return undef (instead of printing
here's an interesting request. i want perl code to have decent access to
some or all of the pod associated with that code.
so, why do we need a way to get at pod (or other doc strings) in the
code? one reason to have it comes from my work on stem. i want a remote
module to be able to spit out a
> It strikes me that this is very fragile and limited (unless I
> misunderstand, which is quite possible).
We've thrashed out a much more comprehensive proposal, which I'll
post this morning.
Damian
Thus it was written in the epistle of Uri Guttman,
>
> how do you tell the above two apart? by array do you mean only an array
> variable? then you can't chomp a list of scalar values or multiple
> arrays, etc.
>
> this needs to be clarified.
Quite true. The two-argument one is new to me and I
> "TA" == Ted Ashton <[EMAIL PROTECTED]> writes:
TA> One-argument chomp():
TA> array:
TA> chomp()s each element of array using $/?
TA> two-argument chomp():
TA> does as above, but using the second argument (which is a scalar, not a
TA>regex)
how do you te
> Most of the requests for deletion seem to begin with, "This isn't
> used..."
>
> To which, "*I* use it." is a very valid argument.
Agreed. The real problem with ?...? is that it complicates the hell out
of the parser. So long as the special magic is retained for m?...?, I
would su
> If there's a warning if a require'd or use'd file is empty, that's more
> than good enough for me.
Already added to V2 of the RFC.
Damian
Thus it was written in the epistle of Uri Guttman,
>
> if a ref to a scalar, it chomps in place. return the ref? the chomped
> char count?
. . . the point of the RFC was to propose making chomp()'s behaviour change
depending on context.
Here's the summary so far as I can tell:
One-argument cho
Nathan Wiger <[EMAIL PROTECTED]> writes:
> > How usable is this ?
> >
> > I may be missing something, but if every variable mentioned in an anonymous
> > block is assumed to be declared with my, then how do you access or modify
> > the value of any variable outside the block ?
> >
> > Graham.
>
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Eliminate the optional C for C etc block declarations
=head1 VERSION
Maintainer: Peter Scott <[EMAIL PROTECTED]>
Date: 8 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Deep Copying, aka, cloning around.
=head1 VERSION
Maintainer: Peter Scott <[EMAIL PROTECTED]>
Date: 8 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 67
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Add change bar functionality to pod
=head1 VERSION
Maintainer: Dan Sugalski <[EMAIL PROTECTED]>
Date: August 08, 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 65
=head1 ABSTRACT
Docume
John Porter writes:
> > If you wanted to make that parsable, pretend that BEGIN and END are
> > the names of functions with prototype (&) which register callbacks.
>
> I agree ... except that, in perl5 at least, you'd need a terminating
> semicolon if that analogy were 100% accurate.
I realized
> "MM" == Michael Mathews <[EMAIL PROTECTED]> writes:
>> >What about a > chomp($foo, '\r\n'); > # or > chomp(, '\r\n');
>> >syntax.
>>
>> Looks an awful lot like: s/\r\n//; to me...
MM> Yep. It should-- that's all chomp does afterall. The difference is
MM> that the proposed chom
Nathan Torkington wrote:
> These aren't normal subroutines because of the way they stack. If I
> had my druthers, I'd make "sub" *forbidden* on such things.
I like that idea. But then, they also shouldn't go into the symbol table.
At least, not as CODE.
> If you wanted to make that parsable,
I'm working on an RFC on module versioning. It'd be done by now, except
my boss and family keep expecting me to work and be fatherly. :-) Let
me get that banged out, and then lets look at adding wildcards to it.
Dan Sugalski said:
> > > * Do we even want to allow after-the-fact chomps, or do it
automagically
> >at read time?
> "Yes" is rather ambiguous.
To clarify: "Yes", we (I) want to allow after-the-fact chomps. As you
alluded to yourself there are times when you may want to chomp strings that
were no
1 - 100 of 195 matches
Mail list logo
