Well, maybe we should use yen (¥) instead. It even looks like a zipper.
(Of course, we'll leave out the little problem that half the people
in Japan would read it as a backslash wannabe...that's not really
a problem since a zipper would only be used where an operator is
expected, and backslash is
At 9:19 PM + 3/20/04, Simon Cozens wrote:
[EMAIL PROTECTED] (Austin Hastings) writes:
> I'm not sure that having quaternary logic in Perl 6 is necessarily a good
> idea. Why stop only at four states?
Total about twelve possible "states" plus junctions, of which eight or nine
would be 'usefu
Dear All,
I think that the broken bar is dangerous. Why:
It can be mixed up with the normal bar |. In some fonts it looks the same.
And to many people it is not 100% clear, which of the two bars is the broken
one and which not.
Off course it is possible to avoid this, but that is not solving the
Austin Hastings wrote:
Oh, and it's "petaQ" not "pitaph".
Umm, no. It's "pitaph", vice "japh". (Better than "gdtsfhogwaph", certainly.)
Oh, then in that case:
You called me a "pain in the ass"?
I should kill you were you stand!!
;-)
BTW, how did you generate that Â, or did y
> -Original Message-
> From: Damian Conway [mailto:[EMAIL PROTECTED]
>
> Austin Hastings wrote:
>
> > Granted. But some pitaph is going to come along and find a
> > novel new use for zip outside of loops. And then it's going
> > to be in an expression of some kind, where the parser wo
[EMAIL PROTECTED] (Austin Hastings) writes:
> > I'm not sure that having quaternary logic in Perl 6 is necessarily a good
> > idea. Why stop only at four states?
>
> Total about twelve possible "states" plus junctions, of which eight or nine
> would be 'useful', and only three would be knowingly u
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Simon Cozens
>
> I'm not sure that having quaternary logic in Perl 6 is necessarily a good
> idea. Why stop only at four states?
Indeed:
undef, unset (disagreeable undef, a la NaN), nocare (always match
Austin Hastings wrote:
Granted. But some pitaph is going to come along and find a novel new use for
> zip outside of loops. And then it's going to be in an expression of some kind,
where the parser won't know what to do...
%hash = @keys  @values;
Oh, and it's "petaQ" not "pitaph".
Hey...wait
I'm not sure that having quaternary logic in Perl 6 is necessarily a good
idea. Why stop only at four states?
--
... though the Japanese must be the most stupid people... I'm sure I
read somewhere that Tokyo has the densest population in the world...
- Gid Holyoake, sdm.
> -Original Message-
> From: Luke Palmer [mailto:[EMAIL PROTECTED]
> Austin Hastings writes:
> > > From: Luke Palmer [mailto:[EMAIL PROTECTED]
> > > Joe Gottman writes:
> > > > 2) Do all of the xor variants have the property that
> > > > chained calls return true if exactly one input
> >
Hi,
On Saturday 20 March 2004 20:09, Will Coleda wrote:
> I am having trouble running a .pbc that includes a call to _dumper
> unless I run it from the top level parrot directory.
>
> bash-2.05a$ cat ./foo.imc
> .sub main
>_dumper($P1)
>end
> .end
>
> .include "library/dumper.imc"
> bash-2
I am having trouble running a .pbc that includes a call to _dumper
unless I run it from the top level parrot directory.
bash-2.05a$ cat ./foo.imc
.sub main
_dumper($P1)
end
.end
.include "library/dumper.imc"
bash-2.05a$ ./parrot -o foo.pbc foo.imc
bash-2.05a$ ./parrot foo.pbc
"VAR1" => null
b
On Mar 19, 2004, at 11:58 AM, Karl Brodowsky wrote:
just for the Emacs-users among you:
C-x 8 < yields « and C-x 8 > yields ».
Nice to know, even though my Emacs only displays empty squares for
these characters. I have yet to figure out how to get it to properly
display Unicode (I'm using 21.3.5
Hello all,
I've been investigating the possibility of creating a MACHINE
DESCRIPTION (aka BACK-END) for GCC to target PARROT. My thinking is
this: If a satisfactory GCC back-end targeting PARROT is created -and-
PARROT is efficient enough (which from reading the documentation thus
far produced
Here are recent numbers with the new method cache:
$ perl tools/dev/parrotbench.pl -c=parrotbench.conf -b=^oo
Numbers are relative to the first one. (lower is better)
parrotj parrot parrotC perl-th perlpython ruby
oo1 100%104%106%98% 83% 54% 70%
oo2 10
Larry Wall wrote:
Well, Leo asked for hints, and I basically said Perl has no problem
sending them. If Parrot has a problem receiving them, that's another
matter. :-)
When there are now hits from languages like Ruby or Smalltalk, then one
single flag will do it: If ever a real Continuation is cr
At 08:57 AM 3/19/2004 +0100, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 10:38 PM +0100 3/18/04, Leopold Toetsch wrote:
>>
>>Which brings up again my warnocked question: How can return
>>continuations get reused?
> Works like this. (No pasm, but it should be obvious)
I was a
On Sat, Mar 20, 2004 at 11:18:08AM -0500, Dan Sugalski wrote:
: At 12:44 PM -0800 3/19/04, Larry Wall wrote:
: >On Fri, Mar 19, 2004 at 08:57:28AM +0100, Leopold Toetsch wrote:
: >: What's the usage of Continuations from HLLs point of view? Can we get
: >: some hints, what is intended?
: >
: >From
At 12:44 PM -0800 3/19/04, Larry Wall wrote:
On Fri, Mar 19, 2004 at 08:57:28AM +0100, Leopold Toetsch wrote:
: What's the usage of Continuations from HLLs point of view? Can we get
: some hints, what is intended?
From the standpoint of Perl 6, I hope to hide continuations far, far
away in a galaxy
Piers Cawley <[EMAIL PROTECTED]> wrote:
> I argue that we have the problems we do (incorrect behaviour of
> continuations, horrible allocation performance) because we chose the
> wrong optimization in the first place. The stack optimizations that are
> in place make sense when you don't have conti
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Larry Wall <[EMAIL PROTECTED]> wrote:
>> On Fri, Mar 19, 2004 at 08:57:28AM +0100, Leopold Toetsch wrote:
>
>>: I'd like to have, if possible a clear indication: that's a plain
>>: function or method call and this is not. I think the possible speedup i
Piers Cawley <[EMAIL PROTECTED]> wrote:
Another f'up WRT Continuations. Here is an example how to setup a
Continuation:
# main.imc
.sub _main
load_bytecode "set_a.imc"
print "main\n"
end
.end
# set_a.imc
.sub _set_a @LOAD
.local pmc cont
print "set_a\n"
newsub .Sub,
Piers Cawley <[EMAIL PROTECTED]> wrote:
> I've been trying to implement a Parrot port of xUnit so we can write
> tests natively in parrot and things were going reasonably well until I
> reached the point where I needed to do exception handling.
> Exception handling hurt my head, badly, so eventual
23 matches
Mail list logo
