no pcre-config
> ok
> 1/1 skipped: various reasons
> All tests successful, 1 subtest skipped.
> Files=1, Tests=1, 0 wallclock secs ( 0.13 cusr + 0.05 csys = 0.18 CPU)
>
>
> Is this output reasonable? Is it what I should expect?
>
> kid51
>
--
Mark J. Reed <[EMAIL PROTECTED]>
t use quotes in
interpolated array indexes, just like Perl5):
"The value is {$array['a key']}" or"The value is ${array['a key']}"
But:
"The value is {1 + 2 - 3}" - no interpolation
"The value is {$x +$y - $z}" - syntax error because it expects the string
starting with $x to be a dereference.
--
Mark J. Reed <[EMAIL PROTECTED]>
> down.
> -- Vaarsuvius, "Order of the Stick"
>http://www.giantitp.com/comics/oots0107.html
>
--
Mark J. Reed <[EMAIL PROTECTED]>
6:01:53PM -0500, Mark J. Reed wrote:
> >On Dec 20, 2007 4:30 PM, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >
> > Just to add another perspective, PHP uses curlies inside of
> > double-quoted strings to indicate various forms of
> > interpolati
otation
marks to make the character/string distinction.
--
Mark J. Reed <[EMAIL PROTECTED]>
5 wiki.
>
> http://www.perlfoundation.org/perl5/index.cgi
>
> Best regards,
> Conrad Schneiker
>
> www.AthenaLab.com
>
>
>
>
--
Mark J. Reed <[EMAIL PROTECTED]>
o make it too hard to layer such language into Perl6,
but I see no point in bending over backwards to make it particularly
easy compared to other domain-specific languages...
--
Mark J. Reed <[EMAIL PROTECTED]>
t the first push fails because the symbol @a was *bound*
to the list. After an ordinary assignment
my @a = (1,2,3);
@a is still an array, which just happens to have been initialized from a list.
@a.push(4); # succeeds
--
Mark J. Reed <[EMAIL PROTECTED]>
ion conflict is mitigated by the fact that many subtraction
expressions will involve sigils; $x-$y can't possibly be a single
identifier.
And multi-word-expressions without hitting the shift key! My RSI thanks you.
--
Mark J. Reed <[EMAIL PROTECTED]>
Such expressions
were covered in John's original message; I said that the presence of
sigils 'mitigated' the problem, not 'eliminated'. It's one of the
reasons I'm still ambivalent..
Overall, though, it's not a deal-breaker for me one way or the other.
--
Mark J. Reed <[EMAIL PROTECTED]>
ers.
That's an Applescript feature that I could do without in Perl. (Not
that anyone was proposing such a thing, just getting my objection out
there preemptively. :))
--
Mark J. Reed <[EMAIL PROTECTED]>
uding other
> languages) may be found here:
>
> http://en.wikipedia.org/wiki/Contraction_(grammar)
>
> Best regards,
> Conrad Schneiker
>
> www.AthenaLab.com
>
> Official Perl 6 Wiki — http://www.perlfoundation.org/perl6
> Official Parrot Wiki — http://www.perlfoundation.org/parrot
>
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
> 2. The Perl 6 language spec itself would specify a basic set of test
> routines built-in to the language, in a Test namespace
That sounds like a good idea, but it would require that the above Test
functionality be included in the automated tests... which runs the
risk of infinite recursion.
low-precidence version of //, been removed?
>>
>> Yes.
>>
> It could be recycled as a "fuzzy Boolean", returning a fractional value
> between +1 and -1, indicating the confidence with which the result is
> offerred. (As in "err, I'm not sure". :-)* )
t;> function.
>
> I like the idea with an unary function, but I have my doubts with the
> two arg comparison function, because it implies O(n²) runtime. But then
> again if the user needs that, he'd have to implement it in O(n²) anyway...
>
> Moritz
>
> --
> Moritz Lenz
> http://moritz.faui2k3.org/ | http://perl-6.de/
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
more) items", then "1
item", but then "no items". So perhaps it's justifiable in Perl6 as
well.
--
Mark J. Reed <[EMAIL PROTECTED]>
ger
value and (1,) is a tuple of length 1, but the empty tuple is
represented by commaless (). Thus len(()) is 0, len((,)) is a syntax
error, len((1,)) is 1, and len((1)) is a type error.
Also, all three of the empty tuple (), the empty list [], and the nil
value None are distinct from each other.
--
Mark J. Reed <[EMAIL PROTECTED]>
extended a
> little bit.
>
> Gerd Pokorra
>
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
s like assignment. If she just
peels the label off her hook and moves it next to his hook, that's
like binding. Either way she's referencing the same object (driving
the same car), but the key copy is a more flexible arrangement.
--
Mark J. Reed <[EMAIL PROTECTED]>
I don't understand why this stuff is confusing; it's not new with Perl
6. There's a long tradition in O-O of distinguishing between the
externally visible accessor and the internal storage - Ruby self.foo
vs @foo, Java this.foo vs setFoo()/getFoo(), etc. In fact the Ruby
case is directly analogous
arameters don't need to Fail..
--
Mark J. Reed <[EMAIL PROTECTED]>
f utility of
the limit parameter, and I can't believe I misremembered. I was even
indignant not too long ago when using some other language/library
which had a split that behaved as I described instead of as it does in
Perl. Javascript, I believe.
Please excuse the cerebroflatulence.
--
Mark J. Reed <[EMAIL PROTECTED]>
on the Perl6 compiler to generate
PIR that handles it more manually?
--
Mark J. Reed <[EMAIL PROTECTED]>
Good point on the other special subscript values. The PIR as
currently being generated couldn't work anyway, since the subscript is
being put in an Int register instead of a PMC one.
On 9/30/08, Moritz Lenz <[EMAIL PROTECTED]> wrote:
> Mark J. Reed wrote:
>> I didn't
he
> function.
>
> --
> Salu2
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
"nonnegative means length, negative means offset" behavior
is just way too counterintuitive IMO.
--
Mark J. Reed <[EMAIL PROTECTED]>
it's worth asking.
Depending on how they interpret the SDK policy: ("an application may
not itself install or launch other executable code by any means,
including without limitation through the use of a plug-in
architecture…"), any VM-based app might be verboten on the iPhone.
--
Mark J. Reed <[EMAIL PROTECTED]>
riginal 'die'?
>
> ...this is what I would expect. If I catch and then rethrow an
> exception, I'd expect the stack trace to continue to show the
> location of the original throw, not the location of the
> rethrow.
I agree. Otherwise, what's the point of 'rethrow'?
--
Mark J. Reed <[EMAIL PROTECTED]>
t.
As a point of comparison, Pugs accepts the operator overload
definition but doesn't honor it; ~$point still returns the generic
"".
--
Mark J. Reed <[EMAIL PROTECTED]>
.com/catalog/perlhks/
> Tech blog- http://use.perl.org/~Ovid/journal/
> Twitter - http://twitter.com/OvidPerl
> Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
.65 usr 0.82 sys +
539.47 cusr 22.60 csys = 564.54 CPU)
Result: FAIL
It would also help if the actual test output weren't overrun with "Use of
uninitialized value". Is that the result of bad tests or bad harness?
--
Mark J. Reed <[EMAIL PROTECTED]>
=6484, 1224 wallclock secs (661.02 cusr + 28.94 csys =
689.96 CPU)
On Thu, Nov 13, 2008 at 6:03 PM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 13, 2008 at 5:31 PM, Ovid <
> [EMAIL PROTECTED]> wrote:
>
>> Now this test passes (r32629), but the Perl 6 test suite is
one(@a) is. I suppose we could define a
> :uniq(true|false) adverb to modify the meaning of one() so we could
> have both interpretations.
>
> Mark Biggar
>
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed <[EMAIL PROTECTED]>
behavior (via a pragma or whatever) so that sqrt()
returns complex numbers, and then sgn() should start behaving on such
numbers.
--
Mark J. Reed <[EMAIL PROTECTED]>
't it make more sense to have
>
> multi sub sgn(Num) -> Num
> multi sub sqrt(Num) -> Num
>
> behave appropriately for real numbers and
>
> multi sub sgn(Complex) -> Complex
> multi sub sqrt(Complex) -> Complex
>
> behave appropriately for complex numb
) can only return one of
three values. As long as it's sufficiently unlikely that a Complex
will show up when the programmer isn't expecting it, I'm fine with
just having sgn() return 0 for 0 and z/abs(z) for everything else.
--
Mark J. Reed <[EMAIL PROTECTED]>
OK, so let's look at the general problem. The structure is this:
doSomething();
while (someCondition())
{
doSomethingElse();
doSomething();
}
...and you want to factor out the doSomething() call so that it only
has to be specified once.
Is that correct, Aristotle?
The "gotcha" is that
On Wed, Dec 3, 2008 at 2:26 PM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> Overall, the goal is to ensure that by the end of the loop the program is in
> the state of having just
> called doSomething(), whether the loop runs or not - while also ensuring that
> the program is
I was just trying to clarify what I think Aristotle was
asking for, and am not saying it's needed. I suspect this might be too
specific a case to worry about, and I'm willing to settle for the
solution in my last message (using an if inside a do or loop block).
--
Mark J. Reed <[EMAIL PROTECTED]>
On Wed, Dec 3, 2008 at 3:42 PM, <[EMAIL PROTECTED]> wrote:
> loop {
>doSomething();
> next if someCondition();
>doSomethingElse();
> }
That loops forever, doesn't it? But I think this works:
loop
{
doSomething();
last unless someCondition();
doSom
On Wed, Dec 3, 2008 at 3:44 PM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 3, 2008 at 3:42 PM, <[EMAIL PROTECTED]> wrote:
>> loop {
>>doSomething();
>> next if someCondition();
>>doSomethingElse();
>> }
>
> That loops fore
otients
typically also involve heavy use of the remainders, and it's only
reasonable that both halves be treated with equal respect in terms of
language support. A way to get both in one fell swoop would be nice
(e.g. Ruby's Integer#divmod), but at the very least, if we have mod
(%), we should have div, too.
--
Mark J. Reed <[EMAIL PROTECTED]>
quot;unqualified" - strip off
the package name (leading stuff before the ::). As long as no other
package in scope defines something named "True", you don't have to
specify the package.
--
Mark J. Reed <[EMAIL PROTECTED]>
urpose Quotient type with the desired
behavior, but maybe Perl6 would benefit from a generic "stealth list"
type, like Lisp's multiple values. Such an object behaves like a
simple scalar, even in list context, but if you use the right methods
you can access additional values beyond the obvious one.
--
Mark J. Reed <[EMAIL PROTECTED]>
rscores
(though I guess the p6 version might switch to hyphens). I know
there's no official preference for camelCase vs wide_names in userland
code, but it still seems a tad inconsistent. Unless it's an
intentional "make the two levels of DB access obviously different"
desig
ler;main' pc 16573 (perl6.pir:166)
Likewise False. Shouldn't those be the same object? Why would qualifying
the name give it a different set of methods?
--
Mark J. Reed <[EMAIL PROTECTED]>
in' pc 16573 (perl6.pir:166)
perl6(37577) malloc: *** error for object 0x2f97160: Non-aligned pointer
being freed (2)
*** set a breakpoint in malloc_error_break to debug
Segmentation fault
Suggestions on next steps? Assuming I have the problem properly identified,
I will be happy to submit an RT, write a test, dive into the PIR ...
--
Mark J. Reed <[EMAIL PROTECTED]>
The subject line should say "Bool::$1" instead of "Bool::$!", btw; I didn't
let go of the shift key fast enough. This is what I get for trying to be
clever.
On Tue, Dec 9, 2008 at 9:50 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> This is a Rakudo issue, which
oes nothing with it but
pass it into some other interface? How does it declare that? It seems like
there still needs to be a generic superrole that means "some non-empty but
unspecified subset of these roles" - maybe "Closable" would work, but it's
not real clear.
--
Mark J. Reed
I'd say look at prior art, but "end" in this role isn't very common. It
shows up in AppleScript, where it does double duty: "end" serves as an index
in ranges ("items 3 through end of someList"), but by itself it returns the
last item, not the last index ("end of someList"), and as a lone index it
ngified:
> pugs> 2 cmp 10
>
-1
>
pugs> (a => 2) cmp (a => 10)
>
1
>
--
Mark J. Reed
ists.
Since Perl 5 has no REPL, I'm not sure where such a spec would go. S20,
maybe, since the debugger is the closest thing?
Sorry if this has come up before; I did a quick search but didn't see any
discussion of it.
--
Mark J. Reed
it?
> ohh but that should have the same error then
> rakudo: list(1).reduce( { $^a + $^b;});
> rakudo 34244: RESULT[1]
> rakudo: list(1).reduce( { $^a + $^b + $^c;});
> rakudo 34244: RESULT[1]
> rakudo: list(1,2).reduce( { $^a + $^b + $^c;});
> rakudo 34244: OUTPUT[Use of uninitialized value]
> okay thats a bit weird
> something inconsistent is going on.
>
--
Mark J. Reed
an
one for every undef in the expansion.
On Mon, Dec 22, 2008 at 4:17 PM, Vasily Chekalkin wrote:
> Mark J. Reed wrote:
>>
>> Arity 2 and a 1-elem list seems to be special-cased; otherwise, it
>> consistently warns once per undefined value in the expansion:
>
> 1-elem List
Rakudo bug or me not understanding
how constraints work?
--
Mark J. Reed
Ok, it works with a $^var in place of $x in the where block.Should
the parameter be visible there under its declared name? If not, then
this is clearly just pilot error, and never mind...
On Wed, Dec 24, 2008 at 6:47 PM, Mark J. Reed wrote:
> I thought this would work:
>
> multi th
}st" };
multi nth($x where { $^x % 10 == 2 && $^x % 100 != 12} ) { "{$x}nd" };
multi nth($x where { $^x % 10 == 3 && $^x % 100 != 13} ) { "{$x}rd" };
multi nth($x) { "{$x}th" };
And as it's just past midnight here in US/Eastern, Merry Christmas to
those who celebrate it!
--
Mark J. Reed
On Thu, Dec 25, 2008 at 12:00 PM, Patrick R. Michaud wrote:
> On Thu, Dec 25, 2008 at 12:53:06AM -0500, Mark J. Reed wrote:
>> I also tried this, but it caused Rakudo to throw a StopIteration and
>> then segfault:
>>
>> for [...@gifts[0..$day-1]].pairs.reverse ->
On Thu, Dec 25, 2008 at 12:39:24PM -0500, Mark J. Reed wrote:
>> On Thu, Dec 25, 2008 at 12:00 PM, Patrick R. Michaud
>> wrote:
>> > On Thu, Dec 25, 2008 at 12:53:06AM -0500, Mark J. Reed wrote:
>> >> I also tried this, but it caused Rakudo to throw a StopIteration
On Thu, Dec 25, 2008 at 1:55 AM, Stephen Weeks wrote:
> Not long ago, Mark J. Reed proclaimed...
>> What's the consensus on how to do an idiomatic countdown loop? I used
>> for [1..$n].reverse...
>
> This: will work eventually:
>for $n..1:by(-1) { ... }
Coo
On Fri, Dec 26, 2008 at 1:45 PM, Stephen Weeks wrote:
> Looks like you found a regression. This has been fixed since r34393.
Confirmed fixed in r34454. Thanks!
--
Mark J. Reed
int.
>my &more_pid_stuff := pid_file_handler($pid_file);
How does binding work with an rvalue like that?
> Or does each yield produce a fresh new continuation object like this?
That would definitely be my vote.
--
Mark J. Reed
ou must use a non-derived(*) form, why not choose something that
means "non-greedy" in English? Maybe "generous"?
(*) Note casual use of "non-" in actual dialogue :)
--
Mark J. Reed
fields, only leading ones, but the output seems to be
correct for both:
> "a b c ".split(/+/).perl.say
["a", "b", "c", ""]
vs Perl5, exhibiting the trailing field chomp:
$ perl -MData::Dumper -le 'print Data::Dumper->new([[split(/\s+/, "a b
c ")]])->Indent(0)->Terse(1)->Dump'
['a','b','c']
--
Mark J. Reed
trailing"?
We really ought to avoid using "left" and "right" to refer to the
beginning and end of text strings.
--
Mark J. Reed
On Mon, Jan 12, 2009 at 4:19 PM, Aristotle Pagaltzis wrote:
> Maybe :h and :t (head/tail).
I like the echo of the csh pathname modifiers there. Unless that
confuses people into thinking that .trim has something to do with
pathname canonicalization...
--
Mark J. Reed
; On the bright side, this already works in Rakudo:
>
> rakudo: say * ~~ Whatever
> rakudo 35577: OUTPUT«1»
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed
he above is perfectly legal
code. Presumably "say $_" would also yield 2, since I gather the for
is looping over ($i).
--
Mark J. Reed
t;
>
> Did you mean "prelude" instead?
>
> Moritz
>
--
Sent from Gmail for mobile | mobile.google.com
Mark J. Reed
ot. Again, nobody said anything about "code points".
We're talking about Perl6's idea of "characters".
--
Mark J. Reed
contextual metaphor. Argot,
> lingo, whatever...
If we're being all linguistical, how about "circumlect"?
--
Mark J. Reed
aining both the expression evaluated and the result of that
expression...
Without bikeshedding the details, does this seem like something worth
including in the language, or something that would better be provided
by a tool external to the language itself?
--
Mark J. Reed
(IO $handle:) is export;
> -our List multi lines (Str $filename);
> -
> -Returns all the lines of a file as a (lazy) List regardless of context.
> -See also C.
> -
> =item prompt
>
> our Str prompt (Str $prompt)
>
> =item Str.readpipe
>
> -=item IO.recv
> -
> -=item IO.seek
> -
> -=item IO.send
> -
> -=item IO.setsockopt
> -
> -=item IO.shutdown
> -
> -=item IO.slurp
> -
> -our Item multi method slurp (IO $handle: *%opts) is export;
> -our Item multi slurp (Str $filename, *%opts);
> -
> -Slurps the entire file into a Str or Buf regardless of context.
> -(See also C.) Whether a Str or Buf is returned depends on
> -the options.
> -
> -=item socket
> -
> =item IO.sysread
>
> =item IO.sysseek
>
> =item IO.syswrite
>
> -=item IO.tell
> +=back
>
> -=item IO.truncate
> +=head1 Removed functions
>
> -=item warn LIST
> +=item IO.eof
>
> -=item Str.warn
> +Gone, see IO::Endable
>
> -Prints a warning just like Perl 5, except that it is always sent to
> -the object in $*DEFERR, which is just standard error ($*ERR).
> -
> -=back
> -
> -=head1 Removed functions
> -
> =item pipe
>
> Gone, see Pipe.pair
>
>
--
Sent from my mobile device
Mark J. Reed
w".
Side question: are HTTP URI's Writable? If so, I imagine that
translates into a PUT. Is there any benefit in abstracting out the
functionality of POST in a way that maps to other resource types?
--
Mark J. Reed
You
have to take the time zone into account only when translating to a
human-readable form. In that case, it makes no sense for time() to
have a :tz adverb.
If an Instant object also represents a point in time irrespective of
location, then there's likewise no point in a :tz adverb.
--
Mark J. Reed
Considering time scales, there are three that significantly
interrelate, and no matter what Perl 6 uses internally, it needs to be
able to convert to and from these:
TAI: continuous count of time using SI seconds as measured by atomic
clocks, 60 seconds in every minute, 60 minutes in every hour, 2
omes
> time-ranges.
>
> Or perhaps don't make them coercible and require an explicit conversion via
> $date.morning or $date.evening or something. (Maybe require $time ∩ $date
> or $time ⊂ $date?)
>
>
> -David
>
>
--
Mark J. Reed
On Fri, Feb 20, 2009 at 2:36 PM, Chris Dolan wrote:
> Yes, just as I said: a constant offset between each of the proposed
> epochs.
No, because the offset is not constant. The delta between TAI and UTC
is currently 34 seconds. Two months ago it was 33 seconds. The next
time there's a leap seco
f it. I
> refer you to DateTime and DateTime::Duration, which provide a reasonable API
> for this.
>
>
> -dave
>
> /*
> http://VegGuide.org http://blog.urth.org
> Your guide to all that's veg House Absolute(ly Pointless)
> */
>
--
Mark J. Reed
u might as well call it a Millisecond or
Microsecond.
> Time
Brings a lot of expectational baggage with it.
--
Mark J. Reed
On Mon, Feb 23, 2009 at 5:01 PM, Graham Barr wrote:
> Juncture
As has already been pointed out, that has extremely high potential for
being confused with Junctions.
--
Mark J. Reed
instead of any of the above? Silently replacing
the assigned value seems like a Bad Idea.
--
Mark J. Reed
I think the use of % for the modulus operator is too deeply ingrained
to repurpose its infix incarnation.
I do quite like the magical postfix %, but I wonder how far it should
go beyond ±:
$x += 5%; # becomes $x += ($x * .05)? Or maybe $x *= 1.05 ?
$x * 5%; # becomes $x * .05 ?
Ok, consider me duly chastised. Sorry for the sidetracking.
On 12/29/07, chromatic <[EMAIL PROTECTED]> wrote:
> On Saturday 29 December 2007 06:56:45 Mark J. Reed wrote:
>
> > Maybe it's just me, but it
> > seems like it will just feed the all-too-common percep
Whitespace is significant in many places. Even in some of the corners
of Perl 5. Perl 6 has a different set of rules, and it will take some
getting used to, but the rules are designed to let you do things as
naturally as possible.This, for instance, works fine:
my @values =
# (1,2,3) # old
Am I the only one having bad flashbacks to Occam, here? (Transputing Will
Change Everything!)
My $0.02, FWIW:
Concurrency is surprising. Humans don't think that way. And programs
aren't written that way - any program represented as a byte stream is
inherently sequential in nature.
Where the s
e's that patch you mentioned? The attachment doesn't
seem to have made it into the archive there...
--
Mark J. Reed <[EMAIL PROTECTED]>
t a static variable,
> +the old Perl 5 trick of "C" to get a static variable,
> because a C variable starts out uninitialized every time through
> -in Perl 6 rather than retaining its previous value.) Native integer
> +in Perl 6 rather than retaining its previous value.) Native integer
> containers that do not support the concept of undefined should be
> initialized to 0 instead. (Native floating-point containers are
> by default initialized to C.) Typed object containers start
>
--
Mark J. Reed <[EMAIL PROTECTED]>
On Jan 23, 2008 8:05 AM, <[EMAIL PROTECTED]> wrote:
> + So if you see the integer stream C<0x69 0x30F>, it
> +needs to be replaced by C<0x30F>.
Typo - that second 0x30F should be 0x209.
--
Mark J. Reed <[EMAIL PROTECTED]>
Sorry if I'm missing something here, since I haven't dived into the
innards of Parrot, but I thought control flow in Parrot was based on
continuations? Presumably 'control exceptions' are really just
lexicaly-scoped exceptions, and exceptions are in turn just
outgoing-only continuations. If you h
7;d say. But is there a LET*
analogue to do it the old way if we want to?
--
Mark J. Reed <[EMAIL PROTECTED]>
s there no problem you can't solve? :)
Thanks!
--
Mark J. Reed <[EMAIL PROTECTED]>
On Feb 8, 2008 4:31 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Tuesday 05 February 2008 20:02:53 Mark J. Reed wrote:
>
> > Ah, macros, is there no problem you can't solve? :)
>
> If my experience with the Perl 5 core is any guide, the problem of too many
> ma
implementation does store numbers as actual numbers, but I don't know
about blocks and lists and such.
--
Mark J. Reed <[EMAIL PROTECTED]>
able comes from a different place than the $? constants.
> >
> thatswhy they are written uppercase.
> You know $*IN is also internal var bat e.g. $*my is user defined. So i
> see there no difference
> if i define a $?var.
>
> herbert
>
--
Mark J. Reed <[EMAIL PROTECTED]>
On Fri, Mar 14, 2008 at 7:18 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> Even if we were to have a "constant" twigil, I dont much like "$?" for it.
> No mnemomic value. For the builtins, it's not the constancy but the fact
> that they let you quey t
a better solution.
>
> OTOH I don't know the impact of not having it. East European or other maybe
> involved folks should speak up now.
>
> > Simon
>
> leo's 2¢
>
> [1] http://en.wikipedia.org/wiki/Basic_Multilingual_Plane
> [2] http://en.wikipedia.org/wiki/UTF-16
> [3] [EMAIL PROTECTED]:~/svn/parrot/leo> find t -name '*.t' | xargs grep -w
> compose
> t/op/string_cs.t:compose S1, S1
> t/pmc/object-mro.t:# ... now some tests which fail to compose the class
> [4] [EMAIL PROTECTED]:~/svn/parrot/leo> ./parrot t/op/string_cs_46.pasm
> ___ǰ___
> 7 8 8 7
>
--
Mark J. Reed <[EMAIL PROTECTED]>
is dropped in
> scope-bound overloading. In other words $x is then always converted
> into the suitable form. But how is that performed in general? IIRC,
> the only generically available form is stringification.
>
> Hmm, thinking twice, the above optimization is admissible only if
> multiplication is commutative irrespective of the type of $x.
>
>
> Regards, TSa.
> --
>
> The Angel of Geometry and the Devil of Algebra fight for the soul
> of any mathematical being. -- Attributed to Hermann Weyl
>
--
Mark J. Reed <[EMAIL PROTECTED]>
ciently different, that's not a requirement. Again, nobody's
going to think you're dividing pathnames.
> Perl is about linguistics, and hence is more concerned with successful
> communication than with pure mathematical platonics.
Which is why I like it so much more than certain of its brethren with
their Orthogonality Ueber Alles attitude. I just don't want to see
that sort of prescriptivity creep in to Perl.
--
Mark J. Reed <[EMAIL PROTECTED]>
201 - 300 of 516 matches
Mail list logo
