,
perhaps it would be better to provide a more direct method of doing
that (preferably using fchdir where available).
--
Aaron Crane ** http://aaroncrane.co.uk/
names should be Cutf-8,
Cutf-16, Cutf-32.
--
Aaron Crane ** http://aaroncrane.co.uk/
, with its suggestion of whatever the Match found?
--
Aaron Crane ** http://aaroncrane.co.uk/
specifies fcntl(F_SETLK) in place of traditional
BSD-ish flock(). I'd be in favour of having .fcntl in IO::POSIX, but
with an additional role providing .flock (IO::Flock, presumably).
--
Aaron Crane ** http://aaroncrane.co.uk/
Daniel Ruoso writes:
Em Qua, 2009-02-04 às 16:45 +, Aaron Crane escreveu:
pugs-comm...@feather.perl6.nl writes:
+=item method Int read($buf is rw, int $length)
I'm not sure that using a native int is the right thing here. If
whatever the implementation uses as int is narrower than
, that doesn't mean users shouldn't get
access to POSIX dup() for when it *is* what they want.
I agree that also providing a less surprising method would be a good
thing, assuming it can be widely implemented. But it needn't live in
IO::POSIX.
--
Aaron Crane ** http://aaroncrane.co.uk/
-accessible way of achieving the same thing.
--
Aaron Crane ** http://aaroncrane.co.uk/
.pod Mon Mar 17 10:37:26 2008
+In any case, list assignment is defined to be arbitrarily lazy,
+insofar is it basically does the obvious copying as long as there
And insofar as.
--
Aaron Crane ** http://aaroncrane.co.uk/
[EMAIL PROTECTED] writes:
+defaults to a sequence of 0 values. If any native type is explicitly
+initialized to C* (the CWhatever type), it is left unitialized.
s[un ( ) it] = 'in';
(Assuming I've got that syntax correct, anyway.)
--
Aaron Crane
still permit things
like $^Item, or caseless letters (Han characters, Japanese kana,
Hangul, Devanagari, Thai, Hebrew, Arabic, etc).
Maybe even may not consist solely of uppercase Latin-script letters;
that would permit uppercase Greek and Cyrillic and so on.
--
Aaron Crane
;
# Now $b is 17
--
Aaron Crane
Daniel Hulme writes:
On Fri, Jun 22, 2007 at 03:40:37PM +0100, Aaron Crane wrote:
my $b = 1 0 || 42;
# Now $b is 17
s/17/42/ or vice-versa, I think.
Uh, yes. Serves me right for trying to change metasyntactic numbers
midstream.
--
Aaron Crane
and
Presumably that should be number of times.
--
Aaron Crane
there's certainly motivation to wrap this up in a function or
operator, it doesn't strike me as something particularly difficult, or
necessarily more worthy of inclusion in Perl 6.0.0 than anything else.
--
Aaron Crane
). But I need these operations
does not imply Perl 6.0.0 needs these operations.
--
Aaron Crane
[EMAIL PROTECTED] writes:
+be referred to as C COMPILING$?LINE if the bare C$?LINE would
That looks like it's missing a double-colon.
--
Aaron Crane
), and also reads it one further time (to determine the
result of the addition), so it's undefined.
--
Aaron Crane
[EMAIL PROTECTED] writes:
+the top rule. This may be overridden in either the base grammar or a
+derived grammer by explicitly naming a rule top, or defining your
There's a typo there -- grammer for grammar.
--
Aaron Crane
regexes to always use
the Cm or Crx prefix sounds inadvisable on Huffman grounds.
--
Aaron Crane
[EMAIL PROTECTED] writes:
+To pass a regex with leading whitespace you must use the parenthsized form.
...
+To pass a string with leading whitespace you must use the parenthsized form.
Hi. I think that needs an s:g/parenthsized/parenthesized/
--
Aaron Crane
... # with unmatched pointies
}
--
Aaron Crane
to say value-based?
--
Aaron Crane
[EMAIL PROTECTED] commits:
+If the first character is a plus or minus, the initial identifier taken
+as a character class, so
s/taken/is taken/
--
Aaron Crane
in declarations:
my $foo is context;
say CONTEXT::$foo;
versus
my $foo is ambient;
say AMBIENT::$foo;
--
Aaron Crane
statement_modifier:if from
statement_control:if, for both humans and the compiler. One option might
be to require an extra token (a postfix complementizer?) before a statement
modifier. Maybe something like this:
return $foo
--- if $something;
--
Aaron Crane
{...} instead of @{[...]}
is definitely a good thing.
--
Aaron Crane
the last
time I encountered it was on a dot-matrix printer manufactured in the
1980s.
Hmmm. Encode.pm doesn't seem to have support available for any of the
ISO 646 character sets. I feel a patch coming on.
--
Aaron Crane
.
--
Aaron Crane
internally, for example.
Just for kicks, this one demonstrates all the features. It's the same as
before, but in descending order:
@unsorted
== sort infix:=, desc = 1, key = { $_.foo('bar').compute }
== @sorted;
What problems can anyone spot with this suggestion?
--
Aaron Crane * GBdirect
Luke Palmer wrote:
Aaron Crane writes:
@unsorted
== sort infix:=, desc = 1, key = { $_.foo('bar').compute }
== @sorted;
I don't like the Cdesc flag. But I can't, at the moment, think of any
way around it short of:
@unsorted
== sort { $^b = $^a }, key = { .foo
a
sub, for example.
--
Aaron Crane * GBdirect Ltd.
http://training.gbdirect.co.uk/courses/perl/
(). That is, should the
programmer be allowed to determine whether two apparently-identical
numbers have the same representation, or should .id() fudge the issue by
pretending that all representations of a number of a given type are
identical.
--
Aaron Crane * GBdirect Ltd.
http
Sean O'Rourke writes:
On Thu, 5 Dec 2002, Sean O'Rourke wrote:
how 'bout tang for Tog's A Negated Grep?
Gah. s/Tog/Tang/.
Wouldn't that mean we had to rename grep to 'gnat'? (Gnat's Not A Tang,
presumably, never mind rot13 and reversal...)
--
Aaron Crane * GBdirect Ltd.
http
in @ARGV which
matched.
I'm not so fond of that -- I don't think it's as obvious that you're doing a
two-way classification.
--
Aaron Crane * GBdirect Ltd.
http://training.gbdirect.co.uk/courses/perl/
as an extra 'you might also see this'
affair.
Anyway, that was a bit of a rant, but what I mean is: I'd actually be
in favour of avoiding backtick entirely in operators.
--
Aaron Crane * GBdirect Ltd.
http://training.gbdirect.co.uk/courses/perl/
along at home, I think that means the match
operator has to be ~~ or =~, but I can live happily with either of those.
--
Aaron Crane * GBdirect Ltd.
http://training.gbdirect.co.uk/course/perl/
, the rule ordering didn't matter with the add a leading ^ to
hype rule.
I think I prefer the first one, by the way -- it strikes me as more
obviously a vector add.
--
Aaron Crane * GBdirect Ltd.
http://training.gbdirect.co.uk/courses/perl/
) the parens are required. And in Icon it's done
with backtracking, not superpositions.
--
Aaron Crane * GBdirect Ltd.
http://training.gbdirect.co.uk/courses/perl/
38 matches
Mail list logo
