On 11/27/2002 7:54 PM, Angel Faus wrote:
For example, the integer 30 can be written in base 16
in two equivalent ways:
my $x = 16#1D;
my $x = 16#1:14;
These two representations are incompatible, so writing
something like C<16#D:13> will generate a compile-time
error.
Ambiguity:
Is C equiv
On Wed, Nov 27, 2002 at 08:28:42PM -0500, James Mastros wrote:
> >This won't work for bases greater than 36, so we
> >have too:
> Grammar: I think this should be "so we also have:", or possibly "so we
> also have...".
The colon is more correct, the ellipsis means this is a quotation that
I've sho
"Bryan C. Warnock" wrote:
>
> On Tue, 2002-11-26 at 13:36, Michael Lazzaro wrote:
> > The main difference is that p6-docs is intended to move very narrowly
> > from topic to topic, in a roughly predetermined order, focusing on each
>
> But not to move faster than the design of the language.
Yeah
Hi,
Would it be possible to rename the $PARROT/languages/Befunge-93
directory into $PARROT/languages/befunge ?
Indeed, as soon as parrot will support objects, I'll implement the
befunge 98 specs, and the same interpreter will be able to interpret 93
ou 98 befunge code...
I'm sorry, 'cause I
Dan Sugalski sent the following bits through the ether:
> Also, at the moment I can't test this
OK, I've had a go. I'm basing the following on the code you mentioned
at http://use.perl.org/~Elian/journal/9147 (of course, you should know
better than to use "exit" in parrot assembler ;-) and basic
James Mastros wrote:
On 11/27/2002 7:54 PM, Angel Faus wrote:
For example, the integer 30 can be written in base 16
in two equivalent ways:
my $x = 16#1D;
my $x = 16#1:14;
These two representations are incompatible, so writing
something like C<16#D:13> will generate a compile-time
error
On Thu, 2002-11-28 at 18:08, Richard Nuttall wrote:
> James Mastros wrote:
>
> > On 11/27/2002 7:54 PM, Angel Faus wrote:
> >
> >> For example, the integer 30 can be written in base 16
> >> in two equivalent ways:
> >>
> >>my $x = 16#1D;
> >>my $x = 16#1:14;
> >>
> >> These two representat
On Thu, 2002-11-28 at 14:59, Michael Lazzaro wrote:
> But my worries are that we could not keep P6L sufficiently focused,
> resulting in an even *bigger* tangle of threads; that we can't really
> *have* the discussions without posting the proposed documentation too;
> and that P6L would not respond
Jonathan Scott Duff wrote:
> BTW, is 256#2_3_4:255 legal? I vote no.
Correct: an underline may exist only between digits; technically, the
2,3 and 4 aren't digits; the two digits in the above are 234 and 255.
> I was under the impression that Perl6 would support bigints natively
> such that when
Angel Faus wrote:
>
> A few questions, about stuff I am not sure I got right. Sorry if this
> has already been resolved.
>
> - What is the default behaviour (without using any pragma) of 1/0?
> NaN or exception?
Unknown (open issue). :-(
> - Are these correct? What will they do?
>
> my In
Dave Whipp wrote:
> Perhaps an example will clarify my thoughts
>
> my $big_heavy_object = Foo.new;
> $big_heavy_object = add($big_heavy_object, $bar);
>
> If the context provides access to the lvalue, then it
> may be possible to optimize. Effectively, we have the
> information to create an
On Thu, 2002-11-28 at 18:47, Bryan C. Warnock wrote:
> Yes, but the first digit is 0. Or, more accurately, 0 * 16**2.
Hmmph. Some accuracy. 0 * 16**1
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
12 matches
Mail list logo
