Re: Time::Local

tainly sortable: year first, then month, then mday. 2005-07-05T20:01:42+0200 Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Time::Local

don't USE numbers for week days! So beginning at 1 makes no sense, except for humans who like creating lists like (undef, ). In fact, I would prefer to not having any 0 :) Now, for months, yes it does make lots of sense. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convo

Re: Time::Local

itrarily chosen day for the first. Or, well, for compatibility, Sunday :) Computers and Perl count from 0. People count from 1. If something begins at 1, it is expected to be a people's thing. And with week days, this just doesn't work, as not everyone's week starts at the same d

Re: DBI v2 - The Plan and How You Can Help

ld be fun if we could just steal that design and build on top of it, for compatibility, but also because other people have already thought about it and proven that it works. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

WTF? - Re: method calls on $self

.method(...); } was the perfect solution. Killing off a useful and much used idiom even before the first release is quite an accomplishment. Disallowing .method here means a huge step back in time. Back to $_.method or $object.method. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Perl 6 Summary for 2005-07-05 through 2005-07-12

s includes any method/submethod with an explicitly > named invocant, I hope. No, $?SELF exists in every method. It's not the *default* invocant variable, it's the *always there* invocant variable. There is no default variable anywhere in the language that isn't $_. Juerd

Re: WTF? - Re: method calls on $self

's forced and used to test patience. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: WTF? - Re: method calls on $self

well. Would this mean that $? is an alias for $?SELF, or only that "$?." comes in "./"'s stead? Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: WTF? - Re: method calls on $self

ause it will run all standard Perl 6 code too, as the thing that the fork introduces used to be an error. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: WTF? - Re: method calls on $self

without arguments would also need to be forbidden, following this way of thinking. We can only hope our dictator turns benevolent again, at least regarding the one thing we all agree about (and have agreed about for quite some time): that .foo must always mean $_.foo. Juerd -- http://con

Re: Perl 6 Meta Object Protocols and $object.meta.isa(?)

Larry Wall skribis 2005-08-09 16:19 (-0700): > So either something in the context tells us what "Foo" means, or > it will be taken as a list operator that hasn't been declared yet. Is there, by the way, a pragma to force predeclaration of subs, to gain compile time typo check

Re: Does list construction create new containers?

is can be (but that doesn't mean will be) optimized to $foo =:= $foo which in turn could be optimized to truth. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: @array = $scalar

; # Correct? Yes, although at some point there was this weird notion of scalars automatically dereferencing in list context, in this respect Perl 6 currently is sane. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: @array = $scalar

[EMAIL PROTECTED] skribis 2005-08-31 15:50 (+): > I think this deserves at least a compile time warning and also a > strict pragma to make it an error as it is most likely not what the > programmer wanted. I do not think that using a scalar in list context deserves a warning. Juerd

Re: @array = $scalar

al, chained operators like comma, junction constructors and infix zip, don't get an op= variant. There's something nice in $foo = 42; $foo |= .bar for @quux; as an alternative for $foo = any 42, @quux>>.bar; though Juerd -- http://convolution.nl/maak_juerd_blij.html h

Re: @array = $scalar

Stuart Cook skribis 2005-09-01 22:49 (+1000): > [1] i.e. magically applies itself to any valid infix operator, just > like »« and [] do , is not a normal binary infix operator. It's not even binary, although it can of course be used with only two operands. Juerd -- http://con

Re: for $arrayref {...}

t context not being Array context. It does not dereference anything. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: for $arrayref {...}

of your variable, that means that you flatten yourself > into specific kinds of contexts. sub foo (@bar) { ... } foo $aref; Here $aref is dereferenced because of the Array context. The scalar can't do this by itself, of course. Juerd -- http://convolution.nl/maak_juerd_blij.h

Re: Proposal: split ternary ?? :: into binary ?? and //

Thomas Sandlass skribis 2005-09-05 14:38 (+0200): >b) if this is true, ?? evaluates its rhs such that it > can't be undef But $foo ?? undef // 1 then is a problem. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy

perl6-language@perl.org

Luke Palmer skribis 2005-09-06 13:28 (+): > Well, we'd better document that pretty damn well then, and provide > min_arity and max_arity, too. Won't junctions do Array, then? I think &foo.arity.max would be very intuitive, and likewise, for @&foo.arity

Re: \(...)?

esting (and imho, a bad idea), because: > \(@array); # same as \(@array) and [EMAIL PROTECTED] are the same thing > \(@array,); # same as \(@array,) is [ @array ], NOT map { \$_ } @array Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happ

Re: Proposal: split ternary ?? :: into binary ?? and //

go ahead and make > it ??!!. (At least this week...) I was going to object based on !!foo being ! ! foo, but that !! is spelled ? now, so nevermind. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

$bar; AFAIK, these are the same thing, because the left side of [0] is in Array context, which is a scalar context, in which comma creates a new anonymous array ref. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

ot the nonexistent second element of the nonexistent list. > sub *postcircumfix:<[ ]> ([EMAIL PROTECTED]) { Do postfix list operators exist in Perl 6? AFAIK, the only thing that can create a list is list context, and I'm very unsure how anything that can handle both a list a

Re: \(...)?

ovided the new insight about comma creating an array of aliases rather than copies, I retract this. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

se they do not construct) works very well in Perl 6: it is not the parens that construct the array in scalar context, it is something else. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

item and slurpy

Are "item context" and "slurpy context" official terms yet? (Note that "official" is temporary, not permament, and has nothing to do with things being set in stone.) If so, then are the keywords for forcing context also "item" and "slurpy",

Re: item and slurpy

iscussion about this so that it can be settled. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

coercion and context

o ways (at least) to test for ability to coerce, as this can happen lossily and losslessly. Thinks like $foo.canbe(Int) and $foo.fitsin(Int) came to mind, but single word method names are probably better, if only someone can think of any. Juerd -- http://convolution.nl/maak_juerd_b

Re: coercion and context

t are the implications of that)? What role does coercion play > in multimethod dispatch? Good questions. Relevant regardless of coercion syntax. I have no idea. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

do? Are parens in any way special when used with \? What is the precedence of \? Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

the case, I suggest we rename \ to something that actually LOOKS like a function, that is: something with a \w+ name. This all would imply that its precedence is lower than comma. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

foo($a,$b); > or not? I think this works, but I was discussing syntax: the function of parens after \, and how to look at \ compared to other \W and \w+ operators, syntax wise. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: conditional wrapper blocks

legant programming way too easy and attractive, and that its benefits are far too little. At first glances, it makes me think it's mostly useful for people who hate refactoring. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: conditional wrapper blocks

;d actually prefer something like: for my $item (@menu) { my $label = encode_entities $item->label; my $href = uri_escape $item->url; my $there = $item->there; print qq[$label\n] if $there; print qq[$label] if not $

Re: Stringification, numification, and booleanification of pairs

pair can be confused for its key or value. A good alternative is hard to find, though. I tend to prefer 1 at this moment (coincidentally, that's +?$pair). Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: \(...)?

ke sense to try and figure out a Perl signature for it? > Because the comma operator supplies list context, (@a, @b) flattens > @a and @b, so it's like @a.concat(@b). Ah, comma supplies list context regardless of the context the comma is in? Is this current, or part of your proposa

Re: Stringification, numification, and booleanification of pairs

ut is there also something like :(2...)th? > On 9/21/05, Juerd <[EMAIL PROTECTED]> wrote: Please reply properly: below quotation (not above), per subject (usually: per paragraph), and stripping useless junk like signatures. > -- Speaking of signatures... Instruct your mailer to use si

Re: Stringification, numification, and booleanification of pairs

the case. This is also why I'm not sure stringification is done by a prefix:<~> method -- it's probably done by something that does coercion in general, but I have no idea what the syntax for that would be. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution

Re: Stringification, numification, and booleanification of pairs

that ?+$pair should also be true. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

pause/cont

can think of no good way or reason to make this work: FOO: ... { BAR: ... { pause FOO; } } Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Stringification, numification, and booleanification of pairs

lity, and is a very bad thing. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: pause/cont

the scenes is > not a bad thing :) I still consider sub calls, loops, conditions, etc, to be controlled forms of goto. They're good-goto. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Stringification, numification, and booleanification of pairs

string > representation of the entire value"). But will they also see "foo" ~ $bar as something different from "foo$bar"? And what context does "foo{ $bar }" use? In my opinion, making the string value in interpolation different from the value in Str co

Re: Stringification, numification, and booleanification of pairs

ation of operator " " with a string and an item. I see a shorter way to write "foo" ~ $bar, as implemented by the circumfix "" operator. > $TSa.greeting := "HaloO"; # mind the echo! echo off Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Stringification, numification, and booleanification of pairs

= 2; my $baz = foo($bar *= 2, 1|2|3); say $bar; The foo call line evaluates to: my $baz = foo(4, 1) | foo(4, 2) | foo(4, 3); # Except that the 4 is really $bar, the lvalue return value of *= not to: my $baz = foo($bar *= 2, 1) | foo($bar *= 2, 2) | foo($bar *= 2, 3); S

Re: .chars, .bytes, etc.

rs. The difference with @foo without .elems would then be non-Num item context: item @foo returns [EMAIL PROTECTED], but item @foo.elems returns [EMAIL PROTECTED] Still, I'd prefer not having .elems at all, as it adds nothing but confusion, regardless of which of the two semantic sets is chosen.

k, v

%hash.kvzip(%hash.k, %hash.v) With hashes and pairs, I don't think there could be any confusion over the meaning of "k" and "v", just like "kv" works without explanation. (Not having to type "alue" also makes it easier for a pair to NOT evaluat

Re: k, v

ct .pairs to return pairs, not keys and values zipped. Re each, I don't know what to expect: a single pair, or all pairs. Not what .kv does, anyway. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Stringification, numification, and booleanification of pairs

ean. > Which often looks like madness until you realize that it's just a > reflection of how most hackers think. ;-) This calls for a poll, because I believe nothing of this "most". Hackers on this list, what do you think? Juerd -- http://convolution.nl/maak_juerd_blij.ht

Re: Stringification, numification, and booleanification of pairs

number number stringnumber join scalarnumber ref This huge difference in how smart an array is makes it kind of useless to take Perl 5 as an example of how arrays should behave in Perl 6, because that would also dictate that "foo" ~ @bar end in the number of elements in @bar. B

matching colors (was Stringification, numification, and booleanification of pairs)

s > bluish red ;-) We can do better than equivalence testing for colors. Instead, try to match. Surely a *smart* match operator really is smart? $color ~~ '#FF00FF' == $color ~~ 'magenta' == $color ~~ [ 255, 0, 255 ] Juerd -- http://co

Re: Stringification, numification, and booleanification of pairs

y IS confusing! It is NOT TRUE that strings with variables interpolated are always for presentation. It is NOT TRUE that uninterpolated strings are always for storage. Both can be used either way, and in practice are used both ways. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Stringification, numification, and booleanification of pairs

f it without reading a book. Yes, if things are different, they should be really different. For this reason I want ~$foo and +$foo be different where something making sense can be thought of and implemented without much effort, and pairs to evaluate to something OTHER than their values (the

numification and stringification of objects

a protocol. In fact, I cannot think of any object class that would have multiple possible stringifications, and none of them obviously more important than others. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Stringification, numification, and booleanification of pairs

t strings so you > can customize it, including ways to change the defaults for a class > (like the separator for arrays of pairs being "\n" instead of ' '). Just the way I imagined it. Great! Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: .chars, .bytes, etc.

context, both return the number of elements. > BTW, does everybody expect more than one prefix numerifyer beeing > redundant or is there an idea of (+ (+ @foo)) beeing modelled It's providing context to something that was already providing context. A bit redundant indeed. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

.thingies in contexts

split should be called "chunks" and behave as described in this message. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Sort of "do it once" feature request...

the global state of syntactic flip flops makes me be afraid of using them in subs. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Sort of "do it once" feature request...

TSa skribis 2005-09-26 19:39 (+0200): > Sorry, I'm totally out of scope to what 'the flipflop operator' is. > Could you be so kind to give some hints. Thanks in advance. http://perldoc.perl.org/perlop.html#Range-Operators Juerd -- http://convolution.nl/maak

Re: Sort of "do it once" feature request...

TSa skribis 2005-09-26 20:32 (+0200): > Does someone consider this 'inner boolean state' and the 'magical > auto-increment algorithm if the operands are strings' of the Perl5 > range op a feature worth preserving? Yes, many someones do. Juerd -- http://convolution

perl6-language@perl.org

be. That's why the equivalent of $& will be usable without any frowning. > Grtz, Ruud K vnd grtz n btj mljk t lzn, n d z mt ntrljk n s zjn. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: This week's summary

r me, the most noticeable difference is the time spent thinking and writing: for replies it's short, for new messages, it's long. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

zip: stop when and where?

What should zip do given 1..3 and 1..6? (a) 1 1 2 2 3 3 4 5 6 (b) 1 1 2 2 3 3 undef 4 undef 5 undef 6 (c) 1 1 2 2 3 3 (d) fail I'd want c, mostly because of code like for @foo Y 0... -> $foo, $i { ... } Pugs currently does b. Juerd -- http://convolution.nl/maak_juerd_blij.h

Re: zip: stop when and where?

nnot know whether a list is finite? my @foo = slurp ...; # lazy, but can be either finite or infinite my @bar = 1..10; say @foo Y @bar; # ? Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: zip: stop when and where?

$xyzzy { ... } And even though for @foo Y @bar Y @baz -> $quux, $xyzzy { ... } is something you will probably not see very often, it's still legal Perl, even though it looks asymmetric. This too makes finding the solution in arguments a non-solution. Juerd -- http://convolution.nl

Re: $value but lexically ...

Luke Palmer skribis 2005-10-06 14:23 (-0600): > my role is_default {} # empty > sub foo($a, ?$b = 0 but is_default) {...} Would this work too? 0 but role {} Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html

Re: Type annotations

uot;hello" can't in a useful way be coerced to a number If it dies because of b, very good. If because of a, I think we have a huge difference of opinion regarding automatic coercion. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Type annotations

Exception "hello 5 worlds"? /^<...>/ perhaps? And I think we should match against Num, not Int, as it's very hard to have a rule that matches just integers. 0.5e3 is an integer, but 0.5e-3 is not. As stated in my previous message, I think that all numbers should be parsed t

Re: Type annotations

Yuval Kogman skribis 2005-10-07 12:53 (+0200): > On Fri, Oct 07, 2005 at 12:42:01 +0200, Juerd wrote: > > For my Int $c = $float, though, I'd want coercion. > > And I think it is wrong to have such a huge difference between literals > > and values: if a variable coerces,

Re: $value but lexically ...

Miroslav Silovic skribis 2005-10-07 13:07 (+0200): > Can an inline role be named? > 0 but role is_default {} This is a nice idea. It would require named roles (and to really be succesful, also classes, subs, methods, ...) declarations to be expressions, but I see no downside to that.

Re: Type annotations

seconds. It's nice to get all the certain failures during compile > > time. > How about in unreachable code (which I do actually believe compilers can > detect some of the time)? I'm quite ambivalent about this. Juerd -- http://convolution.nl/maak_juerd_bli

Re: $value but lexically ...

turn &bar; > } > foo(42).(); # Does this mean that this Perl 5 snippet no longer does the same in Perl 6? { my $foo = 5; sub bar { return $foo; } } Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/mak

Re: Sane (less insane) pair semantics

ARGS or something like that to be a *-able array that will be guaranteed to be compatible with the current sub's signature. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Sane (less insane) pair semantics

foo(([EMAIL PROTECTED])); foo ([EMAIL PROTECTED]); This doesn't allow for combining named and positional pairs. I do not think that is necessary at all, for arrays. I think that combining the two on the same level is a recipe for disaster anyway, and should perhaps even emit a w

Re: Sane (less insane) pair semantics

Juerd skribis 2005-10-10 15:20 (+0200): > only pairs on the topmost level of arguments (not in any parens) are s/not in any parens/not in any grouping parens/, to exclude .() Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution

Re: Sane (less insane) pair semantics

is very arguable. (Very little sidenote: parameters are expected, arguments are passed. In the signature, you have parameters, in the call, you have arguments. However, in the case of a named argument, it does make some sense to call the name parameter and the value argument, resulting in having

Re: Sane (less insane) pair semantics

lso indicates, confusing at best. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Sane (less insane) pair semantics

nfix and circumfix parts. Please leave the parens for grouping (and in calls: breaking recognition). Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

feather

an on making these available through a web interface soon. There are no data backups for feather. I am considering weekly backups. Do you think they are needed? Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: multiline comments

Alfie John skribis 2005-10-12 15:28 (+1000): > Does Perl6 support multiline comments? All incarnations of Perl have allowed us to begin multiple subsequent lines with the comment glyph '#'. I am sure Perl 6 will not break this tradition. Juerd -- http://convolution.nl/maak_juerd_b

Re: Translitteration and combining strings and array references

a feature to trans entire strings? i.e. 'foo' => 'bar', where foo is a single thing replaced by bar. Does this not exclude any possibility of specifying ranges in strings? Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Re(vised): Proposal to make class method non-inheritable

ot;Perl 5-ism" can be construed as positive or negative. Please do elaborate. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Translitteration and combining strings and array references

Luke Palmer skribis 2005-10-18 11:57 (-0600): > It looks nicer if you use the indirect object form: > trans "string": [ > => "0", > ]; It'd also look very nice with optional parens: "string".trans [ => "0" ]

Re: Making Wrong Code Type Wrong

encoding. In that case I suggest the "lit" operator that provides Str::Literal context&coercion, which coerces to any other string type without encoding. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Making Wrong Code Type Wrong

gt; it can't always be easily re-encoded. Encoding functions should therefor > > check if a variable does safe::(none()) and warn or fail if so. > I don't see how this relates to the OP, or why encoding functions > should implement it like this. The "should" is

Re: syntax for accessing multiple versions of a module

DBI; use MyDBI as DBI; Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: Re(vised): Proposal to make class method non-inheritable

Larry Wall skribis 2005-10-19 1:43 (-0700): > On Tue, Oct 18, 2005 at 04:43:57PM +0200, Juerd wrote: > : dot sigils are not actually special. They are required on has-variables > : and forbidden on all other. Changing them to be optional is trivial, or > : so I hope. > Dot sigils

Re: Re(vised): Proposal to make class method non-inheritable

This takes away my objections to the dot twigil entirely. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: new sigil

nal keyboards? 3. What is the ASCII equivalent? 4. Why not ^, which is available? 5. Why is the sigil needed? Pairs do well without, too. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: new sigil

Juerd skribis 2005-10-20 17:03 (+0200): > 3. What is the ASCII equivalent? Suggestion: 1c 'c' is an invalid character in numbers, and currently only numbers can begin with a digit. 1cFoo The 1 provides an extra visual hint of the cheapness of the class. J

Re: new sigil

Juerd skribis 2005-10-20 17:03 (+0200): > 4. Why not ^, which is available? Or the euro symbol, which also has a C in it. It doesn't always have to be American ;) It's in iso-8859-15, which is compatible enough with iso-8859-1 to support ¥ and both « and ». (I hope those turn out

Re: new sigil

will have its equivalent too. (It's ^KCt in vim, btw) Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: new sigil

Larry Wall skribis 2005-10-20 8:46 (-0700): > On Thu, Oct 20, 2005 at 05:35:10PM +0200, Juerd wrote: > : I'm sure ¢ will have its equivalent too. > c| or C| maybe. But sub c { ... } sub d { ... } if $foo eq c|d { ... } Juerd -- http://convolution.nl/maak_juerd_

Re: new sigil

Schneelocke skribis 2005-10-20 18:00 (+0200): > Would c! be an option? In current Perl 6: Yes, because infix ! does not exist. But several people want ! to be a chainy none() constructor, and this would destroy a dream. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution

Re: new sigil

gestion instead of just telling us > why our ideas don't work in very specific circumstances, feel free. I've already suggested two. Is that not enough? (a) ^ (b) 1c Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: new sigil

oks like h (hash). I dislike things like "$calar" and "@rray", and now some people will use "¢lass" in examples. Please let that the sigil looks like a certain leter not be a reason. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: new sigil

eady overstepping a boundary. It's perfectly normal to have one glyph do very different things according to how/where it's used. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

Re: new sigil

Steve Peters skribis 2005-10-21 6:07 (-0500): > Older versions of Eclipse are not able to enter these characters. That's > where the copy and paste comes in. That's where upgrades come in. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_

Re: new sigil

fore Perl 6 is released. Juerd -- http://convolution.nl/maak_juerd_blij.html http://convolution.nl/make_juerd_happy.html http://convolution.nl/gajigu_juerd_n.html

  1   2   3   4   5   6   7   8   >