perl5 has a facility to dump the optree in XML,
which is currently not regression tested.
Ive submitted a test-file which tests the XML output
against a few golden-samples, but its been ignored/overlooked.
So let me ask:
is MAD XML output used in any way currently (or in future) ?
is there a
On Mon, Aug 10, 2009 at 10:31 AM, Carl Mäsak wrote:
> In my post "Three things in Perl 6 that aren't so great" [0], I
> outline three things about Perl 6 that bug me at present. Commenter
> daxim made what seems to me a sensible proposal [1] for solving the
> third problem, "Comments in the begin
On Tue, Aug 11, 2009 at 8:59 AM, Jon Lang wrote:
> Ben Morrow wrote:
> > However, I would much rather see a general syntax like
> >
> >(# ... )
> >{# ... }
> >[# ... ]
> >
>
a preceding ':' (colon) makes it *notionally*
a null-label-block-comment-construct.
>
> > with no whitespace
Luke Palmer wrote:
It's likely that CPAN will have a Bundle::EYEWTIBWATA. [1]
[1] Everything You Ever Wanted To Install But Were Afraid To Ask
EYEWTIBWATL eye-witty-bwattle
.. But Were Always Too Lazy
since the qq:X family has recently come up, Id like to suggest another.
qq:i {} is just like qq{} except that when it interpolates variables,
those which are undefined are preserved literally.
its purpose would be to support the construction of strings for
subsequent eval'g, particularly where you
Rich Morin wrote:
> At 11:24 PM -0500 3/6/02, Uri Guttman wrote:
>
>> qn would be just like qq but not allow any
>> direct hash interpolations (%foo or %foo{bar}). you can always get those
>> with $() if needed. this solves the common case with a minimal of noise
>> and the uncommon case h
so, assuming we have;
print 'you gave me: @wordlist = ';# single quote - no interpolation
for @words -> $it {
print;
FIRST { print '(' }# provisionally
NEXT { print ',' }
LAST {print ');' }
}
# and maybe
else {
print "();\n";
}
this yields:
you gave me: @wo
Dan Sugalski wrote:
> At 1:07 PM -0400 4/30/02, Miko O'Sullivan wrote:
>
>> > Damian, now having terrible visions of someone suggesting
>> C ;-)
>>
>> Then may I also give you nightmares on: elsdo, elsdont, elsgrep,
>> elstry ...
>
>
> Has anyone brought up elselse or unlessunless yet?
>
and
Damian Conway wrote:
>Luke Palmer wrote:
>
>>Ooh! Why don't we have a dont command! With several variants:
>>dont FILE
>>dont BLOCK
>>
>>dont { print "Boo" }
>>
>>Would print:
>>
>>
>
>You really *should* be more careful what you wish for Luke.
>The following was just uploaded to
with p5, Ive often written
eval {} or carp "$@ blah";
it seems to work, and it reads nicer (to my eye) than
eval {}; if ($@) {}
but I surmise that it works cuz the return-value from the block is non-zero,
for successful eval, and 0 or undef when block dies, not cuz of magical
treatment of $@
ive oft wondered how a constant/parameter namespace could be designed to:
- lighten Exporter symbol export in perl 5
- expose (for example) POSIX constants in only the contexts where
theyre meaningful
within a POSIX call - ex various c-open flags (im too lazy
to cite any cu
Damian Conway wrote:
Can I suggest that an alternative solution might be the following:
So an L2R array-processing chain is:
@out = @a ~> grep {...} ~> map {...} ~> sort;
There might also be a be special rule that, if the RHS is
a variable, the LHS is simply assigned to it.
[EMAIL PROTECTED] wrote:
Shouldn't access to 'is computed' arrays be read-only?
If you want to be able to consume the elements by shifting,
you can always create a tied object that kees a cursor and
a reference to the underlying array and gives you that
access (and it could die for splicing, etc
13 matches
Mail list logo
