tested, but you get the idea...
Or, a slightly different syntax from yours:
schwartzian {
first {...}
sort {...}
last {...}
} @ary;
--Brent Dax
Excuse typos, it's hahd to write on a Palm...
>>>>>> "Brent" == Brent Dax <[EMAIL PROTECTED]> writes:
> Brent> @s = schwartzian(
> Please, if we're going to add an operator, let's not call it schwartzian!
> I have enough trouble already telling people how to spell my name. :)
W
New Magic to Perl.
>- Keep your eyes on
>modularity. Modularity is by
>far the best concept where
>complexity could be hidden.
>
>- Don't forget usability. This
>is after all the point why
>people use Perl in the first
>place.
Never.
So the basic question is, readability or usability? I say usability.
--Brent Dax
Excuse typos, it's hahd to write on a Palm...
-Original Message-
From: Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 15.43
To: Brent Dax
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Perl culture, perl readabillity
>> The reward? English-speaking children learn what is arguably th
I think we were all just stunned by the sheer brilliance. :^) That package
thing is pretty damn clever...
--Brent Dax
[EMAIL PROTECTED]
This e-mail is a circumvention device as defined by the Digital Millennium
Copyright Act.
#qrpff
s''$/=\2048;while(<>){G=29;R=142;if((@a=unq
[EMAIL PROTECTED] wrote on 4/5/01 12.15:
>2. package vs. module/class
>Whoa. This is so simple yet so sublime. It solves so many issues in one
swoop. Cool.
>Assuming Perl6 will be parsing Perl5 code? Hmmm. That's interesting. Forget
p52p6 and the whole 80/20 thing, we could potentially hit the
.
How about $a cat $b? That keeps the theme of strings using words and
numbers using symbols--like eq vs. ==.
--Brent Dax
... (cue X-Files theme)
So, what else would we do with our new inline #! notation? Hmm...
$foo=$bar;
#!comment
yadda yadda yadda
blah blah blah
foo bar baz
#!endcomment
$bar.=$baz;
Maybe? Possibly? No? Darn...
--Brent Dax
[EMAIL PROTECTED]
essed?) references, and
concat otherwise.
Does any of that make sense? Or should I be returned to my straightjacket?
:^)
--Brent Dax
[EMAIL PROTECTED]
t should be slurpy, I suppose. Damn...
--Brent Dax <[EMAIL PROTECTED]>
Perl and Parrot hacker
;> ()/) {
return {
if($cond) {
$expr1; #Last expression is the return value, right?
}
else {
$expr2;
}
};
}
Thanks, Larry!
--Brent Dax <[EMAIL PROTECTED]>
Perl and Parrot hacker
Piers. Enjoy *that*. ;^)
--Brent Dax <[EMAIL PROTECTED]>
Perl and Parrot hacker
"Yeah, and my underwear is flame-retardant--that doesn't mean I'm gonna
set myself on fire to prove it."
ays "remember my old value whenever I'm
assigned to." We'll call this 'undoable'. In this case:
@a is undoable; #@a=() is noticed, @a[0] isn't
@a are undoable;#@a[0] is noticed, @a=() isn't (or maybe it is?)
#i could have used has/have instead, but is/are makes more sense here
--Brent Dax
[EMAIL PROTECTED]
sub bar is property(variable) { #property that attaches to the variable
...
}
Even if it was actually implemented some other way, all we'd need to do is
make sure that we can attach properties to it somehow. (The C
property would itself attach to a variable, not a value.)
--Brent Dax
[EMAIL PROTECTED]
Simon Cozens:
>On Sun, May 20, 2001 at 01:09:28AM -0700, Brent Dax wrote:
>> This also reads like English:
>> Is foo constant?
> Until you realise that in order to actually use it sensibly, you'll
have to say something like
> if (is $foo constant)
>
has exactly one meaning,
regardless of context. It also gives () back its C meaning, grouping stuff
together so it'll be evaluated first, instead of a meaning that can be
different in different contexts. (In general, I think that "syntactic
operators" like parenthesis and comma shoul
I'd think that @ISA would be copied to .ISA on object instantiation, and
after that the two wouldn't have anything to do with each other. We could
set up one of those cool copy-on-write locks everyone's been talking about
to save memory too.
Or we could have it default to @ISA if .ISA doesn't ex
5
print "Baz: $(Baz('a', 'b'))"; #prints Baz: b
print "Baz: @(Baz('a', 'b'))"; #prints Baz: a b
print "$(Context)"; #prints scalar
print "@(Context)"; #prints list
Does that check out right?
Thanks,
--Brent Dax
[EMAIL PROTECTED]
o -language. :^) )
BTW, one other random thought I came up with while I was writing this: Could
inheritance be a
property?
class My::Class is a('Other::Class'); #My::Class::ISA=('Other::Class')
--Brent Dax
[EMAIL PROTECTED]
nse in any computer language. You may have an idea,
# but you are saying it wrong if you do.
There are plenty of things that have no counterpart in boolean logic. Where are loops
defined in
Boolean logic?
--Brent Dax
[EMAIL PROTECTED]
et me know.)
Thanks,
--Brent Dax
[EMAIL PROTECTED]
27;d have to turn it on explicitly.
Could we use this so that we don't have to use 'ref' (or its moral
equivalent) in method lookups? In other words, if $spot is declared to
hold a Dog, can we assume that it does, thus skipping the check with
'ref' normally used for method dispatch? Would this even buy us
anything? Why am I asking myself these questions? Why are the
orderlies putting me in a white truck?
--Brent Dax
[EMAIL PROTECTED]
# -Original Message-
# From: Uri Guttman [mailto:[EMAIL PROTECTED]]
# Sent: Friday, August 24, 2001 8:56 PM
# To: [EMAIL PROTECTED]
# Cc: [EMAIL PROTECTED]
# Subject: Re: Will subroutine signatures apply to methods in Perl6
#
#
# >>>>> "BD" == Brent Dax &
I was thinking about Perl 6 today, and thought of something: if the
sigil is now part of a variable's name, does that mean that $Foo::bar
should actually be Foo::$bar in Perl 6?
--Brent Dax
[EMAIL PROTECTED]
od example of a bad use of is-a. It also meant that the class
was nearly impossible to modify for different storage--it was far easier
to just write a new class with the same interface. Stupid, stupid,
stupid.
--Brent Dax
[EMAIL PROTECTED]
eds to know things like endian-ness and for reading precompiled
bytecode anyway, we might as well make it convenient...
--Brent Dax
[EMAIL PROTECTED]
"...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet."
to
the uninitiated.
--Brent Dax
[EMAIL PROTECTED]
"...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet."
$AUTOLOAD is in.)
The second step takes care of resolving the address of the function; it
handles picking which (if any) of the prototypes available for the
method is appropriate for those parameters. Its implementation is left
as an exercise to the reader. :^)
--Brent Dax (who finds it very amu
rograms in the OISC machine language are included.
We now have available have a revised and expanded version of oisc called
OIC. In the future, this may replace OISC."
from http://www.tuxedo.org/~esr/retro/
:^)
--Brent Dax
[EMAIL PROTECTED]
"...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet."
e is in a try block;
otherwise we get the same die-at-compile-time behavior.
In other words, I want exceptions thrown at compile-time to be catchable
at run-time by surrounding try blocks. Are there any barriers to this
working? If so, what are they?
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
Uri Guttman:
# $fh.irs( 'Peterbilt' ) ;
We're going to have an IRS property on filehandles? God, I can hear the
jokes already...
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
-Interpolation
-Operator precedence
-Comparison operators
-And and Or
-Anything not already implemented in Parrot
print() currently only takes one parameter, but you can use ~ to
concatenate things together. It spits out a crapload of debugging
information--symbol ta
Now, will use ~.
With the many different opinions on this, maybe we should
just have three or four different concat operators...
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
_($$)) ($x, $y)
# { $x _ $y }
#
# etc.
Of course. OTOH, people will scratch their heads when they come upon
$foo § $bar or whatever.
On a separate note, how will '$foo??Bar::baz::frob' parse?
Since I've been complaining a lot, I'll now say a bunch of the things I
do like:
^
//
parser that smart?
#
# Just curious...
Hmmph. My guess is that you'd have to do something like <($counter >
1000 ?? $file1 :: $file2)> and the fact that there are open parens at
the first greater-than would be enough for the parser to figure it out.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
I'm back. I notified Simon on the tenth that I was going to be away
until today. I'm trying to catch up on the nine-hundred-odd messages
the p6? and p5p have thrown at me, so I may be realistically out of
commission for a couple days more.
--Brent Dax
[EMAIL PROTECTED]
Configure pu
Those alternate universe syntaxes coming from quantum fluctuations in
# the uncollapsed syntax superposition. I'll soon be firing a polaron
# burst through the main deflector in a desparate attempt to stabilize
# this anomoly before it destroys Perl 6.
All these Star Trek references a
uld seem unfair to ban the use of
colon on method calls, or to make you declare a self; perhaps:
method bar($a, $b: $c, $d) {
...
}
That still leaves the case of C<< $obj->bar($a: $b, $c) >>. Perhaps:
method bar(: $a: $b, $c)
would work f
to know if I'm at least right about the
placement of 'type'.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
*BabyPerl is a program I'm wor
7;apple'); # green
$obj.fruit{apple}
# Regardless of whether something like the above two examples
# can/will be
# auto-created, what would those methods look like anyway?
# Would they simply
# be:
#
# method colors is lvalue { return @.colors }
# method fruit is lvalue { return %.fruit
Damian Conway:
# BTW, colon isn't an operator (it's a separator), so it can't be hyped.
What do you mean? We can hype the colon all we want! :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
#x27; general way to make both a scalar variable
# binding and its
# value constant?
Could you do C<%MY::{'$pre'} is constant> to lock the symbol table
entry?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
ing by someone who
knows more than me. :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
e is the only eccentricy I have left from my early work in (ugh) VB
print $fh: .quux; #same as $me.quux
print $fh: .gerflonkurator; #same as $me.gerflonkurator
}
Cool.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
y for waking up perl6-language. I
had seen almost no traffic on it in weeks, and was starting to get a bit
worried that thoughts on the languages were coughing, sputtering and
dying. :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
think of it as a "skewed or", which is, er,
# both what it both is, and what it looks like.
If we have 'and', 'or' and 'xor', can we have 'dor' (defined or) to be a
low-precedence version of this?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
nsistency, I'd prefer to use is: 3+(2 is i). Well, either way,
this is a good thing for properties to handle. GO PROPERTIES! ;^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
complete
Followed by the catch-all:
Cannot continue after parsing errors
I've pasted a program below that shows much of what it can handle.
babyperl.pl is attached to this e-mail. It's over 600 lines, and very
messy. I will likely rewrite the whole thing Real Soon Now to make it
se should be obvious. In that case, 'scalar'
context is really 'one' context. However, we can still call it scalar
context if it makes you feel better. :^) (Yes, those are just my
opinions. They do not necessarily reflect Larry's, Damian's or the guy
in the padded ce
concatenation) operators (in
perlop).
-The opendir(), readdir(), closedir(), and rename() built-in functions
(in perlfunc).
HTH.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
"Nothing important happened today."
--George III of England's diary entry for 4-Jul-1776
t; ['@argv %argv']}
);
In other files:
use MyModule; #imports everything in export
use MyModule 'quux';#imports only &quux
use MyModule ':argc'#imports @argv and %argv
use MyModule(); #imports nothing
Richard J Cox:
# [EMAIL PROTECTED] (Brent Dax) wrote:
# > krish:
# > # I am a beginner in Perl and have a very trivial query. I have
# > # some .expect
# [...]
# >
# > This is the wrong group for this sort of question.
# perl6-internals is
#
# s/internals/language/
Doh! got the
Bryan C. Warnock:
# On Saturday 22 December 2001 02:29 am, Brent Dax wrote:
# > I've been thinking about improvements that could be made to
# Exporter for
# > Perl 6.
# >
# > 1. Choosing where to export to:
# > use Data::Dumper 'Dumper' => 'd
Michael G Schwern:
# I've rearranged the proposed features a bit to put the long objections
# at the bottom.
#
# Brent Dax wrote:
# > I've been thinking about improvements that could be made to
# Exporter for
# > Perl 6.
# > 3. Warnings about conflicts:
# >
We have an empty 'less' pragma in Perl 5, right?
use less '6';
use less '6' => 'path/to/perl/6/version';
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
"Nothing important happened today."
--George III of England's diary entry for 4-Jul-1776
of the current block
UNDOExecutes on "un-normal" exit of the current block
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking and regex hacker
. hawt sysadmin chx0rs
This is sad. I know of *a* hawt sysamin chx0r.
I know more than a few.
obra: There are tw
oderef;
#
# and then wondering why it says "Undefined LAST block" or some such.
Maybe all of the [A-Z]+'s get defined each time the block is entered
(or, if the block is being iterated on, the first time the block is
entered during this set of iterations).
--Brent Dax
[EMAIL PROTE
difference there.
Nope. 'use Foo;' is translated to 'BEGIN {require Foo; import Foo;}' by
Perl; Exporter just provides a default implementation of import().
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking and regex hacker
. hawt sysadmin chx0rs
This is sad. I know of
. operator?
Still, though, a wonderful piece of code.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking and regex hacker
Check out the Parrot FAQ: http://www.panix.com/~ziggy/parrot.html (no,
it's not mine)
. hawt sysadmin chx0rs
This is sad. I know of *a* hawt sysamin chx0r.
I k
have a Camel III.
The first thing is to open it to Chapter 4, which starts on page 111.
Now, read through Apocalypse 4, highlighting everything that's changed.
Not things that have been added--just things that have changed.
I think you'll find that Perl 6 isn't as dissimilar
Aaron Sherman:
# On Mon, 2002-01-28 at 11:17, Brent Dax wrote:
#
# > I'd like you to perform an exercise for me if you have a Camel III.
#
# I have a Camel 1 (pink) and 2, but not 3. However, I follow
# you. You are
# (as everyone else has fallen into the trap of) thinking of only what
#
d{x}",%d{x})? Is
# that a bug or does it produce "n{x}" where n is the value of
# %d{x} as an
# integer?
It produces something pretty weird. Just single-quote the format string
instead of double-quoting it.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking and regex hacker
note that that still leaves grep as-is, with the old format.
Perhaps that's a clue that we should leave this alone, though perhaps
with the args to map and grep rearranged.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking and regex hacker
Check out the Parrot FAQ: http://www.panix.com/~z
ach node's siblings.
Implementation-wise, things get fairly easy once the vtable->match stuff
I mentioned above is in place. Obviously we would optimize for string
matching. Also, we WILL lose some performance, even over the current
slowdown compared to Perl 5. Nevertheless, it can be
Sure we will. They're just not our first target. We build our own
interpreter/VM, then when that's working we start in on the JVM and/or
..NET back ends.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking and regex hacker
Check out the Parrot FAQ: http://www.panix.com/~ziggy/parrot
your reply and intersperse your text with the text of the
message as appropriate. I and most other people on the Perl 6 lists use
this style--it helps to provide context and remind people what the
discussion is about. Even if your mailer arranges the text so that your
style is easier (as mine does),
else {#which leaves this else dangling!
baz
}
# And can we assume that "on a line by itself" ignores non-$/
# whitespace?
And comments, I imagine.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking, regex hacker, embedding coder, and boy genius
#define priv
%d hash is %s', $bar, %foo;
? After all, interpolating into an sprintf is a bit dangerous anyway
(what if %foo=('%d' => '')?), and you avoid special cases.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#de
seems to
# have some backing and it is clean and unobtrusive.
I think qn counts as weird syntax. I ask again, what's wrong with one
of:
sprintf("%hash\%s", $string);
sprintf(%hash.'%s', $string);
sprintf('%s%s', _%hash, $string);
?
--Brent
ber this or haven't read about it somewhere, open() was once a
hybrid unary and list operator, so "open FOO, 'bar' || die;" worked.) A
minor adjustment in either the language or the user's usage was all that
was necessary to avoid problems with the change
--Brent
Uri Guttman:
# >>>>> "BD" == Brent Dax <[EMAIL PROTECTED]> writes:
#
# BD> I think qn counts as weird syntax. I ask again, what's
# wrong with one
# BD> of:
#
# BD> sprintf("%hash\%s", $string);
#
# BD> sprintf(%h
pport the Perl 5 blockless style.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
#x27;s expecting a binary
operator or Something Else. That's how it handles things like
vs. numeric less-than (<).
I think, that is. I've always heeded Larry's warning from Camel III
that the tokenizer "has been known to induce eating disorders in lab
rats" (p467). :^
y, opcode.pl, pp.c, and
pp_hot.c. (Of course, it's also off an old bleadperl, but I doubt those
files change that actively.)
BTW, so far toke.c hasn't been as bad as I've heard it is. :^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
mention that.
[3] This seems a bit useless to me too. It's probably more useful to
have a /r modifier on the entire regex.
[4] I changed the ordering for this one to avoid an ambiguity.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
ks like and
that this will work on it.
For this simple reason, I highly suggest somehow hijacking curlies
instead, and perhaps making embedded code use two curlies. After all,
regexes are intimidating enough already. :^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
Piers Cawley:
# "Brent Dax" <[EMAIL PROTECTED]> writes:
# > Larry Wall:
# > That's...odd. Is $$ (the variable) going away?
# >
# > # /./s // or /<.>/ ???
# >
# > I think that . is too common a metacharacter to be
# relegated to
Sorry to reply to the same message twice, but I just noticed something.
Larry Wall:
# {n,m}
Isn't that the only use of angle brackets as a quantifier? That's going
to make parsing more difficult...
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_&q
Mark J. Reed:
# On Wed, May 01, 2002 at 12:11:58PM -0700, Brent Dax wrote:
# > It's far too late to make it into 5.8, but it looks like
# it'll be in
# > 5.10 when that comes out (in a year or two).
# .. . . by which time 6.0 will have already been released, right?
#
# Rig
David Wheeler:
# On 4/17/02 10:02 PM, "Brent Dax" <[EMAIL PROTECTED]> claimed:
#
# > I'm working on a preliminary version right now. So far it's been
# > surprisingly easy--touches toke.c, perly.y, opcode.pl, pp.c, and
# > pp_hot.c. (Of course, it'
Allison Randal:
# On Wed, May 01, 2002 at 01:04:10PM -0700, Brent Dax wrote:
# >
# > *bites back sarcastic comment about the pace of Perl 6's
# development*
#
# *fails to squelch reply about the survival rate of prematurely birthed
# babies*
#
# Some things just take time.
I kn
Graham Barr:
# On Wed, May 01, 2002 at 12:17:52PM -0700, David Wheeler wrote:
# > On 5/1/02 12:11 PM, "Brent Dax" <[EMAIL PROTECTED]> claimed:
# >
# > > It's far too late to make it into 5.8, but it looks like
# it'll be in
# > > 5.10 when that come
g all of
# these as holes would be too much IMO.
That's fixed in 5.8--it uses B::Deparse to make a rough version of the
sub. Just hope it isn't a closure.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks
Luke Palmer:
# sub myint($x) { my $i = int $x; $i == $x ? $x : $i }
sub myint($x) { int $x // $x } #assuming it returned undef
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisi
kes sense to me.
I'm sure it's still there. Otherwise there's no way to take a reference
to a scalar.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conformin
all round.
Just because we're trying to make radical changes doesn't mean we can't
make a small sacrifice to the backwards-compatibility gods. After all,
it would be kinda nice if there were users besides p6* list members, and
I doubt it'll work without at least the small sacrifi
ones, obviously).
#
# There. Nearly 3% of the CPAN ported in two fell swoops! ;-)
Why bother? You've already put P::RD and T::B effectively in the core!
;^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternat
nterpreted the same way, but typed a bit differently. It won't
match your regex.
The moral of the story is that you should not try to parse the *MLs with
regexen--use modules instead.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure
\{ \}
| \< !? [ \w+ | \d+ , \d+ ] \>
)
}
}
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and asked how warp
drive worked. We explained some of the hypothetical principles
Larry Wall:
# On Fri, 7 Jun 2002, Damian Conway wrote:
#
# > Brent Dax wrote:
# >
# > > grammar Perl6::Regex {
# > > rule metachar { <[<{(\[\])}>:*+?\\|]>}
# > >
# > > rule ws { [<[\h\v]>|\#\N*]*
mplementing their interpreters in Perl... ;^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and asked how warp
drive worked. We explained some of the hypothetical principles . . .
&qu
next>/ && $best &&
# $0.length < $best.length {
# }
# fail unless $best;
# let $0 := $best;
# .pos = $best.pos;
# }}
#
# then:
#
# "bacamus" =~ / /;
Will that handle captures correctly? Maybe you should temporiz
er a valid delimiter, and if you want a balanced
one '[' is usually ideal.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and asked how warp
drive worked. We explained
tation language) and a willingness to dig
# through the Apocalypses and Exegeses. (Well, that and not minding the
# first version likely getting tossed out when we do the final
# implementation... :)
If we can use a real parser (Parse::Yapp, Parse::RecDescent), I'd love
to help. If not...we
and converting those that only
contain pairs.)
# (I hope the answer isn't "white space" . . )
#
#
# [Hi, I'm new around here, so I'll give you the three-line
# introduction. I teach Perl at Monash Uni, my office is in the
# same corridor as Damian's, and I like cats, chocolate, and
# curry. (Not all at once.) ]
Well, any friend of Damian's... :^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
xt() keyword would be like the opposite of want(). Of course,
something like:
context $x: foo();
Might not work.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
ectorization happens, and with the ability to
# define your
# > own array behavior, you can pretty much do this however you
# want anyway.
#
# Yes but it would be nuts to have PDL arrays do things one way
# and inbuilt
# compact arrays do things another way.
No, it wouldn't. PDL is
s.
Autodereferencing happens whenever we have a scalar but we need an array
or hash; autoreferencing happens whenever we have an array or hash but
need a scalar (usually because of scalar assignment, but not
necessarily).
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
David Whipp:
# Brent Dax wrote:
# > $href = hash { %hash }; #B
#
# Why the curlies? if C is a function (ctor), then surely
# these should be parentheses. In this context, parentheses are
# optional, so this could be written
#
#$href = hash %hash;
C is not a function. It&
es in text. :^) ) Reading
this, I noticed a potential problem in :w.
To put it simply, what do these expand to?
m:w/foo [~|bar]/
m:w/[~|bar] foo/
m:w/[~|bar] [^|baz]/
m:w/@foo @bar/
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding
1 - 100 of 324 matches
Mail list logo
