On Fri, Nov 04, 2005 at 08:14:11PM +0100, TSa wrote:
: HaloO,
:
: Larry Wall wrote:
: >On Tue, Oct 25, 2005 at 10:25:48PM -0600, Luke Palmer wrote:
: >: Yeah, I didn't really follow his argument on that one. I, too, think
: >: that the one() junction in general is silly, especially for types.
: >
HaloO,
Larry Wall wrote:
On Tue, Oct 25, 2005 at 10:25:48PM -0600, Luke Palmer wrote:
: Yeah, I didn't really follow his argument on that one. I, too, think
: that the one() junction in general is silly, especially for types.
Well, I think it's silly too. I'm just trying to see if we need to
On Tue, Oct 25, 2005 at 10:25:48PM -0600, Luke Palmer wrote:
: Yeah, I didn't really follow his argument on that one. I, too, think
: that the one() junction in general is silly, especially for types.
Well, I think it's silly too. I'm just trying to see if we need to
reserve the syntax in case s
> And in fact, its very existence defies another implicit principle of
> mine, that is, the "principle of partial definition": Defining a new
> type or instance can only break a previously typechecking program by
> making it ambiguous. The idea behind that is that at some time you
> may realize t
On 10/25/05, Eric <[EMAIL PROTECTED]> wrote:
> I would just like to mention that 'class' is confusing because you
> don't realy mean class there. The whole conversation is about types
> so why not have it be 'type'?
If you read the introduction to theory.pod[1], you'll find that we are
actually t
On 10/25/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 26, 2005 at 01:17:10AM +0200, Juerd wrote:
> : Larry Wall skribis 2005-10-25 15:51 (-0700):
> : > ^T would still have to be a placeholder variable.
> :
> : Which it is, in a way.
>
> Though we don't currently allow placeholders in ord
On Wed, Oct 26, 2005 at 01:17:10AM +0200, Juerd wrote:
: Larry Wall skribis 2005-10-25 15:51 (-0700):
: > ^T would still have to be a placeholder variable.
:
: Which it is, in a way.
Though we don't currently allow placeholders in ordinary sigs, or even
in conjunction with ordinary sigs.
: Still
Jan Dubois skribis 2005-10-25 12:33 (-0700):
> Just something to keep in mind in case you are tempted to use the Won
> sign as a sigil or operator in the future.
I don't know what stitch() will do, but this will have to be its infix
operator :)
zip ¥ Y
stitch w
Juerd
--
h
On Tue, 25 Oct 2005, Larry Wall wrote:
> As for the ¥ pitfall, so far we've intentionally been careful to use
> it only where an operator is expected, whereas \ is legal only where a
> term is expected. So at least for Perl code, we can translate legacy
> ¥ to different codepoints. (Whether the J
Larry Wall skribis 2005-10-25 15:51 (-0700):
> ^T would still have to be a placeholder variable.
Which it is, in a way.
Still, I don't think ^ as a sigil needs to mean the same thing as ^ as a
twigil. Visually similar pairs are also not related:
?foo$?foo
*foo$*foo
+f
On Tue, Oct 25, 2005 at 11:44:35PM +0200, Juerd wrote:
: Larry Wall skribis 2005-10-25 14:35 (-0700):
: > On Thu, Oct 20, 2005 at 11:18:14AM -0600, Eric wrote:
: > : Actualy i think ^ might be my favorite so far.
: > : sub sametype (^T $x, ^T $y) {...}
: > I thought that, too, until I realized it w
Larry Wall skribis 2005-10-25 14:35 (-0700):
> On Thu, Oct 20, 2005 at 11:18:14AM -0600, Eric wrote:
> : Actualy i think ^ might be my favorite so far.
> : sub sametype (^T $x, ^T $y) {...}
> I thought that, too, until I realized it wouldn't work as an rvalue:
> ^T.count # 1's complement of nu
On Thu, Oct 20, 2005 at 09:59:49AM -0600, Luke Palmer wrote:
: How about this:
:
: sub foo(c|T $x) {
: my sub util (c|T $in) {...}
: util($x)
: }
:
: Is that c|T in util() a new, free type variable, or am I asserting
: that the type of util()'s argument must be the same ty
On Thu, Oct 20, 2005 at 11:18:14AM -0600, Eric wrote:
: Actualy i think ^ might be my favorite so far.
:
: sub sametype (^T $x, ^T $y) {...}
I thought that, too, until I realized it wouldn't work as an rvalue:
^T.count# 1's complement of number of T instances
On top of which, if it did
On Tue, Oct 25, 2005 at 02:02:58PM -0500, Jonathan Scott Duff wrote:
> On Tue, Oct 25, 2005 at 12:18:41PM -0600, Luke Palmer wrote:
> I don't think so. In the first example all the T (or ¢T) are the same
> type after the first ¢T (where the type is bound). In the second one
> you'd get two separ
On Tue, Oct 25, 2005 at 12:18:41PM -0600, Luke Palmer wrote:
> I like that symmetry between &foo and ¢foo. So to get the behavior
> that an outer type variable applies to an inner sub, could I do this:
>
> # a complicated identity function :-)
> sub foo (¢T $x --> ¢T) {
> my sub b
On Tue, Oct 25, 2005 at 01:57:52PM -0400, Rob Kinyon wrote:
: I'm assuming that when you allow
:
: my ¢T := sometype();
:
: you're also allowing
:
: my class T := sometype();
Yes, that's the idea.
: So, what happens when stupid me names a class "class" through
: symbol-table craziness?
On 10/25/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> We're probably converging on a general rule that two or more
> declarations of the same variable in the same scope refer to the
> same entity:
>
> my $x = 1; # outer $x;
> {
> $x = 2; # bound to OU
> Basically, ¢T is a close analog of &t, which is the variableish form
> for "sub t". When used in a declaration, both of them introduce a
> bare name as an alias into whatever scope the declaration is inserting
> symbols, albeit with different syntactic slots. So just as
>
> my &t := { ... }
: On 10/23/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
: > In addition to your handy table, the >> and << french quotes, which are used
: > quite heavily in Perl 6 for both bracketing and hyper operators, also have
: > full width equivalents:
: >
: > 300A;LEFT DOUBLE ANGLE BRACKET;Ps;0;ON;Y;OP
On Sun, Oct 23, 2005 at 10:55:34PM +0900, Dan Kogai wrote:
: To make the matter worse, there are not just one "yen sign" in
: Unicode. Take a look at this.
:
: ¥ U+00A5 YEN SIGN
: ￥ U+FFE5 FULLWIDTH YEN SIGN
:
: Tough they look and groks the same to human, computers handle them
: differently.
On Sat, Oct 22, 2005 at 06:00:38AM -0400, Damian Conway wrote:
: Autrijus wrote:
:
: >Indeed. Somehow I think this makes some sense:
: >
: >sub Bool eqv (|T $x, |T $y) { ... }
:
: Except that it prevents anyone from ever writing:
:
: multi sub circumfix:<| |> (Num $x) { return abs $
On 10/24/05, TSa <[EMAIL PROTECTED]> wrote:
> Does this capturing of the type into ¢T also involve runtime
> code template expansion? That is, if sametype(Int,Int) didn't
> exist it would be compiled on the fly for a call sametype(3,2)?
I think that's up to the implementation. From the language
p
HaloO,
Luke Palmer wrote:
On 10/20/05, Larry Wall <[EMAIL PROTECTED]> wrote:
Another thing I didn't mention is that that binds both the variable
and its class. But the $ variable is of course optional after the
type, so you could just write that
sub sametype (¢T, ¢T) {...}
if you don't a
On Sat, 22 Oct 2005 [EMAIL PROTECTED] wrote:
If we find a lot of yen signs as zip-operators in the standard
library, Japanese would have a big question: "Give up either
Perl6 or Windows. Which do we need?" And I suppose the answer
Hmmm, begins to sound interesting... ;-P
Michele
--
voices
On 10/23/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> Dan Kogai wrote:
> > To make the matter worse, there are not just one "yen sign" in Unicode.
> > Take a look at this.
> >
> > ¥ U+00A5 YEN SIGN
> > ￥ U+FFE5 FULLWIDTH YEN SIGN
> >
> > Tough they look and groks the same to human, computers han
Dan Kogai wrote:
> To make the matter worse, there are not just one "yen sign" in Unicode.
> Take a look at this.
>
> ¥ U+00A5 YEN SIGN
> ￥ U+FFE5 FULLWIDTH YEN SIGN
>
> Tough they look and groks the same to human, computers handle them
> differently. This happened when Unicode Consortium decided
Maeda-san and the list members,
Thank you for raising this issue and sorry for not raising this myself.
On Oct 22, 2005, at 19:42 , Kaoru Maeda wrote:
If we find a lot of yen sign as zip-operator in the standard library,
we have a big question: "Give up either Perl6 or Windows. Which do
we a
> Luke Palmer wrote:
>
>> limited access to system settings.
>> And in those kinds of corporate environments, you're not going to be
>> working with any code but code written in-house. Which means that
>> nobody is going to be using Latin-1, and everyone will be using the
>> ASCII synonyms. What
Luke Palmer wrote:
>> limited access to system settings.
>> And in those kinds of corporate environments, you're not going to be
>> working with any code but code written in-house. Which means that
>> nobody is going to be using Latin-1, and everyone will be using the
>> ASCII synonyms. What's th
Autrijus wrote:
Indeed. Somehow I think this makes some sense:
sub Bool eqv (|T $x, |T $y) { ... }
Except that it prevents anyone from ever writing:
multi sub circumfix:<| |> (Num $x) { return abs $x }
multi sub circumfix:<| |> (Vec $x) { return $x.mag }
which many mathemat
At 3:26 PM +0100 10/22/05, Nicholas Clark wrote:
At the risk of re-enforcing my apparent optimism.
On Thu, Oct 20, 2005 at 04:02:10PM -0700, Darren Duncan wrote:
that the next best one to exploit is ¤ (euro;
unicode=20AC; utf8=E282AC), and the next best is
Woah. You've just demonstrated wh
On Fri, Oct 21, 2005 at 09:35:12AM -0400, Rob Kinyon wrote:
> On 10/21/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> > On Fri, Oct 21, 2005 at 02:37:09PM +0200, Juerd wrote:
> > > Steve Peters skribis 2005-10-21 6:07 (-0500):
> > > > Older versions of Eclipse are not able to enter these characters
Kaoru Maeda writes:
> Darren Duncan wrote:
> > the next best is £
> Isn't that 0x23 in UK? I imagine that someday all the comment lines
> cause syntax errors in UK...
U+00A3 "POUND SIGN" is at 0x23 in ISO 646-GB (aka BS 4730), true.
Fortunately, that character set is almost never used. I think
At the risk of re-enforcing my apparent optimism.
On Thu, Oct 20, 2005 at 04:02:10PM -0700, Darren Duncan wrote:
> that the next best one to exploit is ¤ (euro;
> unicode=20AC; utf8=E282AC), and the next best is
Woah. You've just demonstrated why Euro is far worse than any of the other
"Unicod
-Original Message-
From: Nicholas Clark <[EMAIL PROTECTED]>
> And for anyone who says "upgrade", please note that many firms in the real
world are still forcing a base perl version of 5.005_03 or 5.6.1 for
development. Still.
My weekend project is to demonstrate that you are an optimist.
On Fri, Oct 21, 2005 at 09:42:00AM +0100, Carl Franks wrote:
> Where did you get ALT-155 from?
Code page 437:
http://www.kostis.net/charsets/cp437.htm
On Fri, Oct 21, 2005 at 06:07:47AM -0500, Steve Peters wrote:
> On Fri, Oct 21, 2005 at 09:42:00AM +0100, Carl Franks wrote:
> > Where did you ge
Juerd wrote:
> I do not see why $ and @ couldn't be both a sigil and an infix
> operator, and the same goes for whatever ASCII equivalent ¢ gets.
>
> ^ and | are available for sigil use. (All the closing brackets are too,
> but that would be very confusing because we tend to visually parse those
>
On 10/21/05, Dave Whipp <[EMAIL PROTECTED]> wrote:
> Luke Palmer wrote:
> > And in those kinds of corporate environments, you're not going to be
> > working with any code but code written in-house. Which means that
> > nobody is going to be using Latin-1, and everyone will be using the
> > ASCII s
TSa skribis 2005-10-21 18:54 (+0200):
> My 2¢ is that we should reap ^ from the one junction and promote it to
> become the 'runtime type information carrier' sigil---like the wings
> on the feet of Hermes/Mercury :)
It is not necessary (or sane, but that's an opinion) to reap it from the
junction
HaloO,
Brent 'Dax' Royal-Gordon wrote:
Steve Peters <[EMAIL PROTECTED]> wrote:
~ seems to be available for a sigil, if my reading of S02 is correct, and
the cent sign is replacing :: in all cases. If not (that is $::foo is
still the global variable named foo) then * may also be available.
Luke Palmer wrote:
As I mentioned earlier, most programmers in a corporate environment
>> have
limited access to system settings.
And in those kinds of corporate environments, you're not going to be
working with any code but code written in-house. Which means that
nobody is going to be using L
On Thu, 20 Oct 2005 16:52:04 -0600, Thom Boyer wrote (in part):
Thom> On 10/20/05, Juerd <[EMAIL PROTECTED]> wrote:
>> 2. How can it be typed with X character composition, vim's digraphs
>> and major international keyboards?
For X11 composition, where getting into compose state is up to your X
e
On Fri, Oct 21, 2005 at 05:27:53PM +0200, Schneelocke wrote:
> On 21/10/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> > I honestly don't know or care what flavor of vi I using, since it usually
> > changes depending on what *nix flavor I'm working on. I also don't think
> > that
> > it should mak
On 21/10/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> I honestly don't know or care what flavor of vi I using, since it usually
> changes depending on what *nix flavor I'm working on. I also don't think that
> it should make a difference what editor I'm using with a programming language.
> Others
On Fri, Oct 21, 2005 at 10:30:40AM -0400, Rob Kinyon wrote:
> > > So, you are proposing that the Perl of the Unicode era be limited to
> > > ASCII because a 15 year old editor cannot handle the charset? That's
> > > like suggesting that operating systems should all be bootable from a
> > > single f
On 10/20/05, Juerd <[EMAIL PROTECTED]> wrote:
>
> Larry Wall skribis 2005-10-20 7:56 (-0700):
> > the new sigil is the cent sign, so ::T is now written ¢T instead.
>
> 1. What does it look like? I've never used a cent sign, and have seen
> several.
It looks like a lowercase c with a vertical line
> > So, you are proposing that the Perl of the Unicode era be limited to
> > ASCII because a 15 year old editor cannot handle the charset? That's
> > like suggesting that operating systems should all be bootable from a
> > single floppy because not everyone has access to a CD drive.
>
> I saying th
On 2005-10-21 10:10 AM, "Steve Peters" <[EMAIL PROTECTED]> wrote:
> I saying that, since my up-to-date version of vi on my up-to-date OpenBSD
> can't type, much less even allow me to paste in, a Latin-1 character, this
> is an issue.
If you're using stock vi rather than vim or elvis or at least n
> Speaking of which, the advantage of, say, « over << is that the former
> is _one_ character. But Y, compared to ¥, is one character only as
> well, and is even more visually distinctive with most fonts I know of,
> afaict, so is there any good reason to keep the latter as the
> "official" one?!?
Steve Peters skribis 2005-10-21 9:10 (-0500):
> I saying that, since my up-to-date version of vi on my up-to-date OpenBSD
> can't type, much less even allow me to paste in, a Latin-1 character, this
> is an issue.
You should report this bug. Hopefully, it will then be fixed before Perl
6 is relea
On Thu, 20 Oct 2005, Rutger Vos wrote:
_one_ charachter. But Y, compared to ¥, is one charachter only as well,
and is even more visually distinctive with most fonts I know of, afaict,
so is there any good reason to keep the latter as the "official" one?!?
Do you even need to ask? It's beca
On Fri, Oct 21, 2005 at 09:35:12AM -0400, Rob Kinyon wrote:
> On 10/21/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> > On Fri, Oct 21, 2005 at 02:37:09PM +0200, Juerd wrote:
> > > Steve Peters skribis 2005-10-21 6:07 (-0500):
> > > > Older versions of Eclipse are not able to enter these characters
> For me AltGr + C gives Copyright-symbol "(c)".
For me too, but AltGr + shift + E gives ¢.
/Stefan Lidman
- Original Message -
From: "Steve Peters" <[EMAIL PROTECTED]>
To: "Luke Palmer" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, October 21, 2005 4:21 AM
Subject: Re: new sigil
But I may have to support your code. That's the issue.
Isn't perl6 a
Speaking of which the advantage of, say, « over << is that the former
is _one_ charachter. But Y, compared to ¥, is one charachter only as
well, and is even more visually distinctive with most fonts I know of,
afaict, so is there any good reason to keep the latter as the
"official" one?!?
On 10/21/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 21, 2005 at 02:37:09PM +0200, Juerd wrote:
> > 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 wh
On Fri, Oct 21, 2005 at 02:37:09PM +0200, Juerd wrote:
> 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.
>
That's where lots of money to update to
On 21/10/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 21, 2005 at 09:42:00AM +0100, Carl Franks wrote:
> > Where did you get ALT-155 from?
> >
> > I've just checked the windows Character Map, and ¢ (cent) is ALT-0162
> > ( If it's not in your startmenu, do start -> run -> charmap )
>
>
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_happy.html
http://
Brent 'Dax' Royal-Gordon skribis 2005-10-20 21:42 (-0700):
> @ Array sigil Array sigil
> $ Scalar sigilScalar sigil
> % Hash sigil Hash sigil, modulo
In non-term, it's not a sigil. There cannot be two subsequent terms.
This is why it makes no sense to wa
On Fri, Oct 21, 2005 at 09:42:00AM +0100, Carl Franks wrote:
> Where did you get ALT-155 from?
>
> I've just checked the windows Character Map, and ¢ (cent) is ALT-0162
> ( If it's not in your startmenu, do start -> run -> charmap )
Actually, both work. That's where the issus with the documentat
On Fri, Oct 21, 2005 at 11:03:07AM +0200, Bra??o Tichý wrote:
>
> - Original Message -
> From: "Steve Peters" <[EMAIL PROTECTED]>
> To: "Luke Palmer" <[EMAIL PROTECTED]>
> Cc:
> Sent: Friday, October 21, 2005 4:21 AM
> Subject: Re:
Where did you get ALT-155 from?
I've just checked the windows Character Map, and ¢ (cent) is ALT-0162
( If it's not in your startmenu, do start -> run -> charmap )
It displays in Eclipse (3.1.1) whether the Text File Encoding is set to
Cp1252 (default) or UTF-8 or ISO-8859-1
Cheers,
Carl
Darren Duncan wrote:
In this case, I support the use of any international currency symbol
for use as Perl sigils and/or operators as appropriate. Eg, we
already use $ (dollar; unicode=0024; utf8=24) and ¥ (yen;
unicode=00A5; utf8=C2A5), and I suggest that the next best one to
exploit is ¤ (e
Sam Vilain wrote:
ps, X11 users, if you have any key bound to "AltGr", then "AltGr" + C
might well give you a ¢ sign without any extra reconfiguration.
For me AltGr + C gives Copyright-symbol "©".
(SuSe 9.1, tested in konsole, kwrite and thunderbird)
--
Markus Laire
Steve Peters <[EMAIL PROTECTED]> wrote:
> ~ seems to be available for a sigil, if my reading of S02 is correct, and
> the cent sign is replacing :: in all cases. If not (that is $::foo is
> still the global variable named foo) then * may also be available.
Sigils can't conflict with unary operato
On Thu, Oct 20, 2005 at 10:40:44PM -0400, Rob Kinyon wrote:
> > Surely you aren't suggesting that these non-English speakers do not have
> > access to the ASCII (or EBCDIC) character sets for their editors, are you?
>
> Surely you aren't suggesting that your editor doesn't have access to
> the Lat
> Please let that the sigil looks like a certain leter not be a reason.
>
>
> Juerd
They make for good mnemonics, which isn't necessarily a bad thing for
people coming from languages without them or with fewer
- sebastian
> Surely you aren't suggesting that these non-English speakers do not have
> access to the ASCII (or EBCDIC) character sets for their editors, are you?
Surely you aren't suggesting that your editor doesn't have access to
the Latin-1 charset, are you? Let's take a look at popular editors:
vi - chec
On Thu, Oct 20, 2005 at 04:23:44PM -0600, Luke Palmer wrote:
> On 10/20/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> > Like the old joke goes "Doctor, Doctor, it hurts when I try to type a
> > Latin-1
> > character." "So don't try to type Latin-1 characters!" Instead, many
> > programmers will
Schneelocke skribis 2005-10-21 1:07 (+0200):
> I think the reason why Larry proposed the "¢" is much simpler - it
> looks a bit like a c, which one could associate with "class", similar
> to how $ looks like S (scalar) and @ looks like a (array). :)
And how % looks like h (hash).
I dislike thing
On 10/20/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> As I mentioned earlier, most programmers in a corporate environment have
> limited access to system settings.
And in those kinds of corporate environments, you're not going to be
working with any code but code written in-house. Which means th
On Thu, Oct 20, 2005 at 05:03:27PM -0400, Rob Kinyon wrote:
> On 10/20/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> > I have some serious concerns about using Latin-1 sigils within Perl 6 and
> > the ASCII multi-character aliases. Am I not understanding something that
> > I should see this as an
On 21/10/05, Darren Duncan <[EMAIL PROTECTED]> wrote:
> On the other hand, if you want to use the ¢ due
> to its being conceptually tied to $, that they
> are different units of currency meant to be used
> together, then the ¢ is fine.
I think the reason why Larry proposed the "¢" is much simpler
Speaking briefly, Unicode is the way of the
future, and even many modern systems have strong
support for it. Perl 6 is a language of the
future plus present, not of the past, and
shouldn't be limited by things that are only
issues for older systems while even then being
easy to work-around o
On Thu, 2005-10-20 at 08:45 -0700, Larry Wall wrote:
> More info. ¢T is a scalar variable just like $T, but enforces a
> class view, so you can use it as a class parameter, and pass any
> object to it, but only access the classish aspects of the object.
> The only other big difference is that you
On 10/20/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> Like the old joke goes "Doctor, Doctor, it hurts when I try to type a Latin-1
> character." "So don't try to type Latin-1 characters!" Instead, many
> programmers will to use the ASCII equivolents that will require additional
> keystrokes.
Y
On 10/20/05, Steve Peters <[EMAIL PROTECTED]> wrote:
> I have some serious concerns about using Latin-1 sigils within Perl 6 and
> the ASCII multi-character aliases. Am I not understanding something that
> I should see this as an advantage?
I had the same concern a few months back. I've come to s
On Thu, Oct 20, 2005 at 10:24:23AM -0700, chromatic wrote:
> On Thu, 2005-10-20 at 10:32 -0500, Steve Peters wrote:
>
> > The idea of punishing programmers who choose to use certain operating system
> > or locales just doesn't seem right to me.
>
> Haven't they already acclimated to the punishmen
Luke Palmer skribis 2005-10-20 10:07 (-0600):
> You seem to be forgetting that we do have the longest token rule. So,
> the only way this destroys a dream (and likewise, the only way c|
> doesn't work), is if you have the poor package or class name c and you
> insist on writing c|d or c!d without
On Thu, 2005-10-20 at 10:32 -0500, Steve Peters wrote:
> The idea of punishing programmers who choose to use certain operating system
> or locales just doesn't seem right to me.
Haven't they already acclimated to the punishment of those operating
systems already?
-- c
What about something like:
c\
Then you get
sub sametype (c\T $x, c\T $y) {...}
Not exactly pretty though. c\T
Actualy i think ^ might be my favorite so far.
sub sametype (^T $x, ^T $y) {...}
--
Eric
On Thu, 20 Oct 2005, Larry Wall wrote:
: > c| or C| maybe.
[snip]
: if $foo eq c|d { ... }
Other suggestions welcome.
<| maybe? And what will we make |> do?
Michele
--
Se non te ne frega nulla e lo consideri un motore usa e getta, vai
pure di avviatore, ma e' un vero delitto. Un po' c
On Thu, 20 Oct 2005, Juerd wrote:
All non-ASCII operators have ASCII equivalents:
¥ Y
« <<
» >>
Speaking of which the advantage of, say, « over << is that the former is
_one_ charachter. But Y, compared to ¥, is one charachter only as well,
and is even more visually distincti
On Thu, Oct 20, 2005 at 08:55:46AM -0700, Larry Wall wrote:
> On Thu, Oct 20, 2005 at 05:53:00PM +0200, Juerd wrote:
> : 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.
>
On 10/20/05, Juerd <[EMAIL PROTECTED]> wrote:
> 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.
You seem to be for
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.nl/
On 20/10/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> : But
> :
> : sub c { ... }
> : sub d { ... }
> :
> : if $foo eq c|d { ... }
>
> Other suggestions welcome.
Would c! be an option?
--
schnee
On 10/20/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> Another thing I didn't mention is that that binds both the variable
> and its class. But the $ variable is of course optional after the
> type, so you could just write that
>
> sub sametype (¢T, ¢T) {...}
>
> if you don't actually care about
On Thu, Oct 20, 2005 at 05:53:00PM +0200, Juerd wrote:
: 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 e
On Thu, Oct 20, 2005 at 07:56:09AM -0700, Larry Wall wrote:
: I don't know how long this EuroOSCON net is going to stay up, so I'll be
: brief. I think we're having a new "class" sigil. Where we've been
: writing ::T, that will revert to meaning "an existing class T that
: we just might not see t
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_blij.html
http://c
On Thu, Oct 20, 2005 at 11:46:30AM -0400, John Siracusa wrote:
: On 10/20/05 11:37 AM, Larry Wall wrote:
: > On Thu, Oct 20, 2005 at 10:32:14AM -0500, Steve Peters wrote:
: > : The idea of punishing programmers who choose to use certain operating
system
: > : or locales just doesn't seem right to
On Thu, Oct 20, 2005 at 08:45:25AM -0700, Larry Wall wrote:
: More info. ¢T is a scalar variable just like $T, but enforces a
: class view, so you can use it as a class parameter, and pass any
: object to it, but only access the classish aspects of the object.
And a nice side effect of that is th
On Thu, Oct 20, 2005 at 05:35:10PM +0200, Juerd wrote:
: I'm sure ¢ will have its equivalent too.
c| or C| maybe.
Larry
On 10/20/05 11:37 AM, Larry Wall wrote:
> On Thu, Oct 20, 2005 at 10:32:14AM -0500, Steve Peters wrote:
> : The idea of punishing programmers who choose to use certain operating system
> : or locales just doesn't seem right to me.
>
> That's why we provide ugly ASCII workarounds for all of them.
More info. ¢T is a scalar variable just like $T, but enforces a
class view, so you can use it as a class parameter, and pass any
object to it, but only access the classish aspects of the object.
The only other big difference is that you can use it in the class
syntactic slot, so it's legal to say
On Thu, Oct 20, 2005 at 10:32:14AM -0500, Steve Peters wrote:
: The idea of punishing programmers who choose to use certain operating system
: or locales just doesn't seem right to me.
That's why we provide ugly ASCII workarounds for all of them. We just
haven't decided what the appropriate ugly
Steve Peters skribis 2005-10-20 10:32 (-0500):
> The idea of punishing programmers who choose to use certain operating system
> or locales just doesn't seem right to me.
All non-ASCII operators have ASCII equivalents:
¥ Y
« <<
» >>
I'm sure ¢ will have its equivalent too.
(It'
1 - 100 of 107 matches
Mail list logo
