achy keen. If you pass it to a Python
interpreter, you get what you deserve :) You have used "use syntax"
which falls under the category of "# or whatever" in my message.
Regards,
-- Gregor
On Wed, 2004-04-14 at 18:51, Brent 'Dax' Royal-Gordon wrote:
> Gregor N
> Aaron Sherman wrote:
> > On Wed, 2004-04-14 at 09:29, Gregor N. Purdy wrote:
> >
> >>So, we are moving in a more verbose direction, which is a bummer for
> >>people who like to write one-liners and other tiny programs.
> >
> >
> > per
ture of Perl 6.
#!/usr/bin/perl6
... # Perl 6 stuff here
use 5; # or, whatever
# Perl 5 stuff here
no 5; # or, whatever
# More Perl 6 stuff here
use python; # you get the idea
...
Regards,
-- Gregor
On Wed, 2004-04-14 at 12:59, Aaron Sherman wrote:
> On Wed, 200
So, we are moving in a more verbose direction, which is a bummer for
people who like to write one-liners and other tiny programs.
Assuming only Perl 6 is installed on your system, if your script
started with:
#!/usr/bin/perl
all the stuff about trying to figure out what version you are using
w
Oh, and the form doesn't require you to do the
:set digraph thing. Its always available.
Regards,
-- Gregor
On Fri, 2004-03-19 at 06:16, Gregor N. Purdy wrote:
> For me, (vim 6.2), that is
>
> < < to get «
> > > to get »
>
> after doing
>
&g
For me, (vim 6.2), that is
< < to get «
> > to get »
after doing
:set digraph
(list of available digraphs can be seen by :digraph)
But, I find the above a bit unnerving because I've deleted
the character, and then if I type a certain character next
I haven't.
Vim also allows
< < t
Larry --
So, will "mutatingness" be a context we'll be able to inquire on
in the implementation of a called routine? Or, could we provide
a specialized distinct implementation for mutating that would get
called if .=X() is used? If we are performing some operation on
large data, and we know the en
onway wrote:
> Gregor N. Purdy wrote:
>
> > In the section "He doth fill fields..." we see an example of Fill
> > Justification where two spaces fit between every word. This doesn't
> > give us an idea of how spaces are distributed if the number of
> > sp
ctly*? Is it an error,
does it have some heuristics to guess? What are the edge cases?
Regards,
-- Gregor
On Sat, 2004-02-28 at 07:39, Smylers wrote:
> Gregor N. Purdy writes:
>
> > In "And now at length they overflow their banks." its not clear
> > how an overflow fie
lidity before the program starts"
But, since E7 doesn't come right out and say it, I'm asking for
clarification. Still could be that you are right and there is nothing
to see here, though...
Regards,
-- Gregor
On Sat, 2004-02-28 at 07:46, Smylers wrote:
> Gregor N. Purdy writes:
The Exegesis mentions the Perl6::Slurp module, but I don't see it
on CPAN. Is it just a race condition?
Regards,
-- Gregor
--
Gregor Purdy[EMAIL PROTECTED]
Focus Research, Inc. http://www.focusresearch.com/
In "And now at length they overflow their banks." its not clear
how an overflow field gets tied to its initial non-overflow field.
In the recipe example given, how does it know to go with the
$method field instead of the $prep_time field? Is it basing off
of matching the horizontal extent of the in
In "Thou shalt have my best gown to make thee a pair...", we are
given a reason to use the option syntax vs. the pair constructing
fat comma C<< => >>: "...we're guaranteed that the key of the
resulting pair is a string, that the string [...] contains a valid
identifier, and that the compiler can c
In the section "He doth fill fields..." we see an example of Fill
Justification where two spaces fit between every word. This doesn't
give us an idea of how spaces are distributed if the number of
spaces needed does not divide evenly into the number of interstices.
In the section "More particulars
In "From the crown of his head to the sole of his foot..." (clearly
a reference to a Gilligan's Island episode where Lovey said something
similar :), we have:
:header{ ..., odd => "Act, $act, Scene $scene...", ... }
and below, text indicating that it will
"prepend the act and scene infor
First, thanks Damian for doing this, and good show!
Smylers already pointed out a few errors in the document, but
here are a few others I noticed:
* In "Why, how now, ho! From whence ariseth this?"
We have this near the top:
type FormArgs ::= Str|Array|Pair;
and this be
Luke --
Hmmm... I haven't been practicing my Perl 6, and its been a while
since the last Apocalyptic refresher, but here goes (I'll don a paper
bag preemptively)...
Thinking of that as the equivalent to:
sort {
my ($ta, $tb) = map { $_.foo('bar').compute } ($^a, $^b);
$ta <=> $tb
} @
Luke --
I guess it might be nice to just do that with a block...
my $n;
while { $n++; @accum } < $total {
...;
}
since we already have a nice do-this-then-do-this syntax.
Sure, it looks a little weird in a for loop:
for ($i = 0; $i < $X; { $i++; some_func() }) {
...;
}
but
18 matches
Mail list logo
