This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl should have a print operator
=head1 VERSION
Maintainer: Jon Ericson [EMAIL PROTECTED]
Date: 5 August 2000
Last-Modified: 30 August 2000
Mailing List: [EMAIL PROTECTED]
Version: 3
Number:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Lightweight Threads
=head1 VERSION
Maintainer: Steven McDougall [EMAIL PROTECTED]
Date: 30 Aug 2000
Mailing List: [EMAIL PROTECTED]
Version: 1
Number: 178
=head1 ABSTRACT
A lightweight thread
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Object Class hooks into Cprintf
=head1 VERSION
Maintainer: Mark Biggar [EMAIL PROTECTED]
Date: 30 Aug 2000
Mailing List: [EMAIL PROTECTED]
Version: 1
Number: 180
=head1 ABSTRACT
There needs to
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Formats out of core / New format syntax
=head1 VERSION
Maintainer: Nathan Wiger [EMAIL PROTECTED]
Date: 30 Aug 2000
Mailing List: [EMAIL PROTECTED]
Version: 1
Number: 181
Status:
"David L. Nicol" wrote:
Dan Sugalski wrote:
I do want to have a set of C/XS/whatever sources as part of the test suite
as well--right now perl's test suite only tests the language, and I think
we should also test the HLL interface we present, as it's just as
important in some ways.
Adam Turoff wrote:
A handful of long overdue updates to http://dev.perl.org/rfc have been made:
- All RFCs are now maintained in both POD and HTML.
HTML conversion is courtesy of pod2html.
- More detailed summaries of all RFCs are available, organized by
RFC number and
=head1 VERSION
Date: 31 Aug 2000
Number: 1
Mailing List: [EMAIL PROTECTED]
Chair: Nathan Wiger [EMAIL PROTECTED]
=head1 SUMMARY
The main point which most discussions are currently centering around is
the idea of fundamental embedded objects in Perl 6. With this concept, a
simple
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
my Dog $spot should call a constructor implicitly
=head1 VERSION
Maintainer: Michael Fowler [EMAIL PROTECTED]
Date: 29 August 2000
Last Modified: 31 August 2000
Mailing List: [EMAIL
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl should support an interactive mode.
=head1 VERSION
Maintainer: Ariel Scolnicov [EMAIL PROTECTED]
Date: 31 Aug 2000
Mailing List: [EMAIL PROTECTED]
Version: 1
Number: 184
Status: Developing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Thread Programming Model
=head1 VERSION
Maintainer: Steven McDougall [EMAIL PROTECTED]
Date: 31 Aug 2000
Mailing List: [EMAIL PROTECTED]
Version: 1
Number: 185
Status: Developing
=head1
arrays-of-scalars
Reply-To: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Standard support for opening i/o handles on scalars and
arrays-of-scalars
=head1 VERSION
Maintainer: Eryq (Erik Dorfman) [EMAIL PROTECTED]
Date: 23 Aug
Baris wrote:
We're talking about how we'll write Perl 6 programs, not PDL programs. We
need to ensure that the syntax we create is Perlish.
Aggreed.
But there is nothing wrong with making the syntax user friendly, or am I
totally missing what perl is?
Perl is user-friendly to Perl users.
Jeremy Howard wrote:
The 1st implementation of Perl 6 may not provide all the optimisations we've
come to expect from our data crunching language of choice. For this reason
maybe PDL will continue to exist independently in Perl 6 at least for a
while, although a fair bit of rewriting will be
We're talking about how we'll write Perl 6 programs, not PDL programs. We
need to ensure that the syntax we create is Perlish.
Aggreed.
But there is nothing wrong with making the syntax user friendly, or am I
totally missing what perl is?
Why do we have qw()?
Why do we have "=" as an alias for
Perl supplies an operator for line input - angle brackets. This is no
analogous operator for output. I propose "inverse angle brackets":
"Print this line.\n";
Perl already *has* a print operator: "print". :-)
The problem with what you have there is that it hides the act of
output within
On 31 Aug 2000, Perl6 RFC Librarian wrote:
my format $FILE_FORMAT =
@: @
$name, $ssn
.
Then this is even less different and scary. Get rid of that Cmy and
it's Perl 5.
s/that Cmy/that Cmy and the dollar sign/;
Cheers,
Philip
--
Philip Newton [EMAIL PROTECTED]
=head1 ABSTRACT
There needs to be a way for an object class to define Cprintf format
specifiers for use in formatting objects into strings with Cprintf and
Csprintf.
I find myself agreeing with your sentiment, but the approach in this RFC
is not sufficiently general. Why only provide
Not every (natural) language does it that way; some place the most
important thing -last-. A Japanese Perl might want to say
"darn" STDERR print;
for instance (Japanese is a subject-object-verb language).
Sure; Latin had SOV, and you still see SOV in Romance
when pronouns are involved.
Baris wrote:
Looping through the matrix elements is probably most common thing people
do
in matrix computation. And because of some weird reason I am not aware of,
the only way to do this efficiently is to write your program in C. So
everybody I know sooner or later switches to C because of
* Adam Turoff ([EMAIL PROTECTED]) [31 Aug 2000 17:41]:
A handful of long overdue updates to http://dev.perl.org/rfc have been made:
[...]
- More detailed summaries of all RFCs are available, organized by
RFC number and working group. See http://dev.perl.org/rfc/by-number.html
and
Likely this should be an RFC. I'm too lazy to write it in that format
right now, but I want to send this thing out before it slips my mind
again. Somebody else may pick it up, if he or she wants it. If not, I'll
eventually may have to do it myself.
The articial distinction between
do
At 08:52 AM 8/31/00 -0400, Karl Glazebrook wrote:
Jeremy Howard wrote:
we are after SIMPLE syntax. This means like C, Fortran, IDL and Matlab.
Perl is about working like most people expect.
Yes, we are after simple syntax. We also want to make to hard things
possible. Therefore we
Jeremy Howard wrote:
We're talking about how we'll write Perl 6 programs, not PDL programs. We
need to ensure that the syntax we create is Perlish. It needs to fit in with
the rest of the language--our proposals won't get through if programs look
quite different in sections just because
At 11:38 AM 8/31/00 +0200, Bart Lateur wrote:
The articial distinction between
do BLOCK while condition;
and
EXPR while condition;
should go, because the former is nothing but a subcase of the latter.
Currently, the former executes the do BLOCK at least once, while the
Bart Lateur wrote:
Combine this with the RFC that bare filehandles must die, in favor of
$FH filehandles, and you won't be able to make the distinction between
print $HANDLE, $string;
and
print $string, $string;
Sure you will! Please re-read the precedence rules from the
Karl Glazebrook writes:
: I have a lot of respect for Larry, but as a scientist I distrust all this
: deference to one single authority.
Well, sure, but someone still has to decide who gets the grants. :-)
: I don't know if Larry has any experience in scientific programming of the
: sort PDL
Johan Vromans wrote:
Good work!
Thanks. :-)
Is there any reason left to maintain formats as something internally
special?
Well, as you note in your implementation suggestions, it would be nice
if Perl compiled the format the first time around. Along with the
implicit constructors
Hildo Biersma wrote:
=head1 ABSTRACT
There needs to be a way for an object class to define Cprintf format
specifiers for use in formatting objects into strings with Cprintf and
Csprintf.
I find myself agreeing with your sentiment, but the approach in this RFC
is not sufficiently
I am unemcumbered by any knowledge of the regex engine implementation,
Yeah.
But I do know something about it, and I have already expressed my
informed opinion. Having you come along to say that you don't know
anything about it at all, but that you nevertheless think I am
mistaken, is
Tom Christiansen writes:
However, I really don't want to see 'return' become a kind of 'last'
for do{}. How would I return from a subroutine from within a do loop?
You already can't do that (as it were) from within an eval.
Yes, but 'eval' has the semantics "run this code but don't let
AFAICT we could make it a syntax error iff foo is not used in void context;
Perl must be able to tell whether or not it is used in order to know what
context the result is in, right?
Well, that depends. Often you must delay till run-time. When Perl
simply sees something like:
sub fn {
Tom Christiansen writes:
However, I really don't want to see 'return' become a kind of 'last'
for do{}. How would I return from a subroutine from within a do loop?
You already can't do that (as it were) from within an eval.
Yes, but 'eval' has the semantics "run this code but don't let
However, I really don't want to see 'return' become a kind of 'last'
for do{}. How would I return from a subroutine from within a do loop?
You already can't do that (as it were) from within an eval.
But I while I am not completely bothered by letting the value
dangle here:
($msg,
"TC" == Tom Christiansen [EMAIL PROTECTED] writes:
TC It just kinda irks me here:
TC $total += 2 * do {
TC my $count = 0;
TC for $n (@nums) { $count += $n }
TC $count;
TC };
TC I rather that were:
TC $total += 2 * do {
TC my $count = 0;
TC for $n
Peter Scott writes:
I dunno, maybe a last in a do block whose value is used by
something should be a syntax error. We're talking about code like
$x += do { $y = get_num; last if $y == 99; $y } while defined $y;
right? *Shudder*
Yes, but we're also talking about code like
Chaim Frenkel wrote:
You are now biting off quite a bit.
What good is half a transaction? If transactions are to be useful,
they should be fully supported -- including rolling back stuff some
third party module did to its internal variables. (Maybe that's a
little extreme ;)
I believe that
Okay, here's a list of functions I think should go into variable vtables.
Functions marked with a * will take an optional type offset so we can
handle asking for various permutations of the basic type.
type
name
get_bool
get_string *
get_int *
get_float *
get_value
At 04:43 PM 8/31/00 -0400, Dan Sugalski wrote:
Okay, here's a list of functions I think should go into variable vtables.
Functions marked with a * will take an optional type offset so we can
handle asking for various permutations of the basic type.
Perhaps I'm missing something... Is this for
Ken Fox wrote:
Trolling?
No, I'm not, it's the direction that RFC 61 ends up if you let it
take you there.
fast perl6 becomes, as well as slicing, dicing and scratching your
back, a drop-in replacement for gcc.
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
I'm confused (I might have missed some discussions, being busy in other
fronts) so please bear with my silly questions.
type
The basic set-in-stone types are...?
name
Huh? A name for what? (How does this relate to a 'string'?)
get_bool
Stored as...? char? int? Boolean or
get_int *
get_float *
Could you elaborate on these a lot? What's an 'int'? What's a 'float'?
Having lately been battling a lot with quad ints and doubles vs long doubles
I seriously want this interface not to suck.
I was a tad concerned there, too. I'm hoping one can painlessly
Dan Sugalski wrote:
get_value
set_value
Wouldn't these go on the SV and not on the inner type? Maybe I'm
thinking value when you're saying variable? The following seem useful
on variables too:
before_get_value
after_get_value
before_set_value
after_set_value
There ought to be
Wouldn't these go on the SV and not on the inner type? Maybe I'm
thinking value when you're saying variable? The following seem useful
on variables too:
before_get_value
after_get_value
before_set_value
after_set_value
There ought to be specializations of get_value and
[perl6-language removed from the follow-up]
"David L. Nicol" wrote:
I want to see Perl become a full-blown C/C++ JIT. Since Perl is for
a large part a compatible subset of C I don't see this as unrealistic.
Trolling? First, Perl is more like lisp with a good syntax -- in other
words about as
Jarkko Hietaniemi writes:
I'm not too worried about getting the vtbl right at the first because
it will be pretty obvious how it should go once the code starts to form.
Some planning isn't that painful :-)
Yes. Especially given that vtables are an unbenchmarked change. It'd
be good to
"David L. Nicol" wrote:
No, I'm not, it's the direction that RFC 61 ends up if you let it
take you there.
You seem to be confusing:
(1) linking C code with Perl
with
(2) compiling Perl to C code
There is a world of difference. Swig does (1) pretty well already.
If you want a first
Fisher Mark wrote:
The rest of us with our TVs, VCRs, and so on have only compiled
code in our devices.
I'd buy a microwave that resets to 'JAPH' after a power failure.
Maybe. ;)
- Ken
On Thu 31 Aug, Mark-Jason Dominus wrote:
Summary report 2831
RFC 110: counting matches (Richard Proctor)
An extensive side discussion of
$count = () = m/PAT/g;
developed, including an excursion off into context issues. I have
asked the author to take this idiom
On Wed, Aug 30, 2000 at 11:54:29PM -0400, Mark-Jason Dominus wrote:
The big thing I find missing from this RFC is compelling examples.
You are proposing a major change to the regex engine but you only have
two examples. Both involve only fixed strings and one of them is
artificial. I
On Wed, Aug 30, 2000 at 04:07:51PM -0400, mike mulligan wrote:
Can this be repackaged in such a way that it is a more natural extension of
the existing regexp language?
The RFC notes that the look-behind construct (?= pattern) can almost be
used. Two issues: 1. as currently implemented,
"MD" == Mark-Jason Dominus [EMAIL PROTECTED] writes:
MD The $ cost is paid by every regex in the entire program, whether they
MD used it or not. This is because Perl has no way to tell which regexes
MD use $ and which do not.
actually it is more like which code refers to $ and which
MD One of Uri's suggestions in RFC 158 was to compute $ only for
MD regexes that have a /k modifier. This would solve the $ problem
MD because Perl would compute $ only when asked to, and not for
MD every other regex in the rest of the program.
the rfc was about making $ private
actually it is more like which code refers to $ and which regex that
caem from. the problem stems from $ being a global and not local like
$1.
Say what? They scope the same!
sub foo { /./ }
$_ = "stuff";
/.../;
foo();
print $;
--tom
in any case, i think we have a fair agreement on rfc 158 and i will
freeze it if there is no further comments on it.
In light of this:
$ The string matched by the last successful pattern match (not
counting any matches hidden within a BLOCK or eval() enclosed
by the
Tom Christiansen wrote:
=item Complex filehandle references
my %filesystem;
my $filename = '/etc/shells';
open $filesystem{$filename}, $filename
or die "can't open $filename: $!";
print $filesystem{$filename};
__END__
GLOB{0xa042284}
This goes
Is some technical reason that this can't be done in perl 5? I hate
having to add another pair of braces just to reassure perl that I didn't
forget a comma:
print {$fh{$name}} "data\n";
Indirect objects are very limited in what they can be.
--tom
Tom Christiansen wrote:
Is some technical reason that this can't be done in perl 5? I hate
having to add another pair of braces just to reassure perl that I didn't
forget a comma:
print {$fh{$name}} "data\n";
Indirect objects are very limited in what they can be.
Currently, but
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
JART - Just Another Regression Test
=head1 VERSION
Maintainer: Michael G Schwern [EMAIL PROTECTED]
Date: Aug 30 2000
Mailing List: [EMAIL PROTECTED]
Version: 1
Number: 182
Status:
On Thu, Aug 31, 2000 at 08:02:36AM -0400, David Corbin wrote:
Comments, criticisms, etc. welcome.
Can you put a legend explaining the color code on the pages where the
colors are used?
Look again.
Next request? ;-)
Z.
On Thu, Aug 31, 2000 at 07:08:38PM +1100, iain truskett wrote:
* Adam Turoff ([EMAIL PROTECTED]) [31 Aug 2000 17:41]:
A handful of long overdue updates to http://dev.perl.org/rfc have been made:
[...]
- More detailed summaries of all RFCs are available, organized by
RFC number and
At 03:45 PM 8/31/00 -0600, Nathan Torkington wrote:
Jarkko Hietaniemi writes:
I'm not too worried about getting the vtbl right at the first because
it will be pretty obvious how it should go once the code starts to form.
Some planning isn't that painful :-)
Yes. Especially given that
Dan Sugalski wrote:
Okay, here's a list of functions I think should go into variable vtables.
All the math functions are in here. Can the entries that my type does
not use be replaced with other functions that my type does use?
Functions marked with a * will take an optional type offset
How about
to_string *
from_string *
as generalizations of formatted/pretty input/output and freeze/thaw
(cf printf/Data::Dumper/Storable)?
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
At 04:59 PM 8/31/00 -0400, Buddha Buck wrote:
At 04:43 PM 8/31/00 -0400, Dan Sugalski wrote:
Okay, here's a list of functions I think should go into variable vtables.
Functions marked with a * will take an optional type offset so we can
handle asking for various permutations of the basic type.
"KF" == Ken Fox [EMAIL PROTECTED] writes:
KF Chaim Frenkel wrote:
You are now biting off quite a bit.
KF What good is half a transaction? If transactions are to be useful,
KF they should be fully supported -- including rolling back stuff some
KF third party module did to its internal
At 04:05 PM 8/31/00 -0500, Jarkko Hietaniemi wrote:
I'm confused (I might have missed some discussions, being busy in other
fronts) so please bear with my silly questions.
type
The basic set-in-stone types are...?
int, float, string, ref, hash, array. All of which have multiple levels,
At 03:12 PM 8/31/00 -0600, Tom Christiansen wrote:
get_int *
get_float *
Could you elaborate on these a lot? What's an 'int'? What's a 'float'?
Having lately been battling a lot with quad ints and doubles vs long
doubles
I seriously want this interface not to suck.
I was a
At 05:30 PM 8/31/00 -0400, Ken Fox wrote:
Dan Sugalski wrote:
get_value
set_value
Wouldn't these go on the SV and not on the inner type? Maybe I'm
thinking value when you're saying variable?
Nope. The get/set value functions are for when something knows what the SV
(or whatever we
Buddha Buck wrote:
If I'm stepping on toes here, please tell me...
See my other message today for the RFCs I'm thinking of writing. Buddha--you
and I should probably sought out offline which of us will write what RFC.
RFC 169v2: Matrix Indexing
Cover my $matrix[$x;$y;$z] syntax
Add
Nathan Wiger wrote:
"David L. Nicol" wrote:
@a["$i $j $k","$a $y $z"] # two points in DN n-dim syntax
One problem that immediately jumps out at me is how to do this:
@a[[@x], [@y]];
That is, dynamically get your indices. The above seems ok when you know
them in
Christian Soeller wrote:
No, at least 18. One more piece of semantics that would be appreciated
is optional omission of trailing dimensions in slices, e.g. for a 3-dim
@a:
@a[0:1] == @a[0:1;] == @a[0:1;;]
I'd rather see the ';' be required, but the '(0..)' not be required, so you
could
Jeremy Howard wrote:
I'd rather see the ';' be required, but the '(0..)' not be required, so you
This is not good! There are a lot of routines where it is very useful to
specify a slice as
@a[0]
that should work regardless how many dimensions @a really has. There are
many instances in PDL
From: "Peter Heslin" [EMAIL PROTECTED]
Sent: Thursday, August 31, 2000 10:51 PM
I would propose that your version of the syntax might also function in
the middle of a regexp: /GHI(?`=DEF)JKL(?`=^ABC)MNO/ would match the
start of the alphabet (fixed-length example used for simplicity).
That's
use Thread;
$thread = new Thread \func , @args;
$thread = new Thread sub { ... }, @args;
async { ... };
$result = join $thread;
$thread = this Thread;
@threads = all Thread;
$thread1 == $thread2 and ...
yield();
critical { ... }; # one thread at
$thread = new Thread \func , @args;
$thread = new Thread sub { ... }, @args;
async { ... };
$result = join $thread;
critical { ... }; # one thread at a time in this block
=item Casync BLOCK
Executes BLOCK in a separate thread. Syntactically, Casync BLOCK
works
Adam Turoff wrote:
Look again.
Next request? ;-)
Can you continue to rock? You're kickin' my ass as RFC Librarian. Nice
job.
-Nate :-)
A handful of long overdue updates to http://dev.perl.org/rfc have been made:
- All RFCs are now maintained in both POD and HTML.
HTML conversion is courtesy of pod2html.
- More detailed summaries of all RFCs are available, organized by
RFC number and working group. See
Which kind of "difference"?
From: Mark-Jason Dominus [EMAIL PROTECTED]
Sent: Wednesday, August 30, 2000 11:54 PM
There are two parts to the $ penalty.
The first part [ of $ penalty is ] maintaining the information for $.
Maintaining this information for your prepos() function is going to
incur an identical cost.
I am
(mystery: how
can filling in $ be a lot slower than filling in $1?)
It isn't. It's the same. $1 might even be more expensive than $.
It appears that many people don't understand the problem with $. I
will try to explain.
Maintaining the information required by $1 or $ slows down the
perl6-language-regex
Summary report 2831
RFC 72: The regexp engine should go backward as well as
forward. (Peter Heslin)
This topic did not attract much discussion until the very end of the
week. I sent the author a detailed critique, to which he has not
responded.
RFC 93
Jonathan Scott Duff wrote:
How about something like this?
$re = qr/(\d\d)-(\d\d)-(\d\d)/g;
$re-onmatch_callback(push @list, makedate(^0,^1,^2));
$string =~ $re;
It's not bad, but it loses one thing that I was trying to keep from the
SNOBOL model. If you have (again,
This is beginning to sound like something I would support.
Heavens are we approaching some sort of consensus.
This also addresses one pain in current PDL which is the
difficulty of multi-dim indexing.
Buddha Buck wrote:
Here is a quick summary of the proposal:
In the raw, arrays can be
At 12:09 PM 8/31/00 -0400, Karl Glazebrook wrote:
This is beginning to sound like something I would support.
Heavens are we approaching some sort of consensus.
The one thing the proposal I mentioned doesn't cover is Jeremy's desire to
have $a[$i][$j][$j] be synonymous with $a[[$i,$j,$k]], and
Chaim Frenkel wrote:
This is making the index variable into an a wrapper object.
No it isn't. Or at least it doesn't have to.
Often there is a need to find the key an object was found in a container.
More often in hashes than in arrays.
And I think this discussion belongs in -data.
Perl6 RFC Librarian wrote:
arsenal. The constructs are:
$ref-[[LIST]]
$ref-{{LIST}}
The proposed respective meanings:
$ref-[$elem[0]]-[$elem[1]}-[...]-[$elem[-1]]
$ref-{$elem[0]}-{$elem[1]}-{...}-{$elem[-1]}
why not just use single braces for
Next, what subset of the set-theory should be implemented. Obviously you
refer to the basic and / or / xor, but in real practice, the other operators
can be very useful. Chaining operators (especially with array-based-sets)
can be a performance nightmare.
Unless you use bitwise operators on
On Thu, 31 Aug 2000, David L. Nicol wrote:
Perl looks, and AFAIK has always looked, like "C plus lune noise" to
many people.
I think Perl looks like "C plus moon noise" to former C programmers. I
imagine some people see it and think "Csh plus Awk noise". Perl is a lot
more than
Eric Roode writes:
Useful functions all, no doubt. But I would lobby heavily for a new
set of names -- ones that can be remembered! Quick -- which trims
leading spaces, champ, chump, or chimp?
My favourite: chafe().
Nat
Tom Christiansen writes:
One could argue that do{} should take return so it might have a value,
but this will definitely annoy the C programmers.
So what.
So what is that it *already* annoys us, which is *why* we would like to
last out of a do. Perhaps you should be able to last
Perl6 RFC Librarian wrote:
=head2 Each thread gets its own copy of block-scoped lexicals upon
execution of Cmy
Example 8
#!/my/path/to/perl
foo();
Thread-new(\foo);
sub foo
{
my $a = 1;
print $a++;
}
[prints "11"]
This must be true
I want last, next, etc. to magically work where I want them to:
do {
last if /booger/;
...
} while ( ... );
Nat
On Thu, Aug 31, 2000 at 02:13:23PM -0500, Christopher J. Madsen wrote:
Jonathan Scott Duff writes:
do { ... last; ... }; # exit the block immediately
do { ... next; ... }; # equivalent to last?
do { ... redo; ... }; #
At 11:21 AM 8/31/00 -0600, Tom Christiansen wrote:
I want last, next, etc. to magically work where I want them to:
I too want last to work in do loops.
do {
last if /booger/;
...
} while ( ... );
Special cased for postfix modifiers, or generalized? If so,
what's the return
On Thu, 31 Aug 2000 11:21:26 -0600, Tom Christiansen wrote:
One could argue that do{} should take return so it might have a value,
but this will definitely annoy the C programmers.
So what.
"Annoying" would be to have a situation that is *less* powerful in Perl
than in C, not *more*.
Oh, and
On Thu, 31 Aug 2000 19:59:31 +0200, you wrotc:
tr/\w//dlt # Trim all leading trailing whitespace from $_
Eh, scratch that. Too much caffeine i guess.
tr/\n\r\t //dlt; # Trim some whitespace.
-DZ
--
Tell me your dreams and I will crush them.
On Thu, Aug 31, 2000 at 07:59:31PM +0200, Dan Zetterstrom wrote:
Why not use the "function" we already got, tr? Something like:
tr///l # Translate only _l_eading characters matching.
tr///t # Translate only _t_railing characters matching.
With "Only leading" I mean translate
At 01:35 PM 8/31/00 -0500, Jonathan Scott Duff wrote:
On Thu, Aug 31, 2000 at 07:59:31PM +0200, Dan Zetterstrom wrote:
Why not use the "function" we already got, tr? Something like:
tr///l # Translate only _l_eading characters matching.
tr///t # Translate only _t_railing
On Thu, Aug 31, 2000 at 02:52:10PM -0400, Buddha Buck wrote:
How would you do:
# Writer insists on blank line between paragraphs, first line indented.
# Publisher insists on one paragraph/line, first word ALL CAPS.
{
local $/ = ""; #slurp paragraph at a time.
while (INFILE) {
How would you do:
# Writer insists on blank line between paragraphs, first line indented.
# Publisher insists on one paragraph/line, first word ALL CAPS.
Step 1: Fire the lame publisher. I'm serious. It's amazing
what people tolerate. Some things aren't worth the pane.
{
local $/ = "";
1 - 100 of 134 matches
Mail list logo
