I'm sorry, but I gotta get back on the
no-global grail trail for at least one
more post.
> The granularity [of currying] can be
> controlled on a sub-by-sub or on a
> class-by-class basis.
If one could do something like this:
{
my $src = 'oldname1';
my $dest = 'newname1';
use FileUt
On Tue, Nov 26, 2002 at 09:55:00AM -, Leopold Toetsch wrote:
> +B
> +
> +The Ith integer or floating processor register, mapped in this section.
> +
> +Note: The register with the physical number zero can not be mapped.
> +
> +=begin unimp
> +
Why can't it be mapped? Fundament
On 11/08/2002 12:09 PM, Michael Lazzaro wrote:
If you wish to take part in the discussions (or even just lurk), please
reply to this message. If you have any particular goals that you feel
this list should be addressing, please let us know.
I'll probably lurk here, on and off, via NNTP. So fa
Nicholas Clark wrote:
On Tue, Nov 26, 2002 at 09:55:00AM -, Leopold Toetsch wrote:
+B
+
+The Ith integer or floating processor register, mapped in this section.
+
+Note: The register with the physical number zero can not be mapped.
+
+=begin unimp
+
Why can't it be mapped? Funda
On Tue, Nov 26, 2002 at 01:51:47PM +0100, Leopold Toetsch wrote:
> Either we fix this, or the registers have to be renumbered, so that reg
> #0 is not used. The emit_code for registers could take care of this.
That's a crafty trick. nothing wrong with that :-)
> Currently no architecture has thi
On 11/17/2002 1:11 AM, Dave Storrs wrote:
Arrays know how to manage their own size; they will grow and shrink as
needed when you add or remove elements. You never need to worry about
whether an array has enough space to hold the number of elements you
are about to insert.
Reference to fixed-size
On 11/14/2002 1:58 PM, Angel Faus wrote:
=section ** Pseudo-Numbers
=section *** NaN
The value C ("Not a Number") may be returned by some
functions or operations to signal that the result of a
calculation (for example, division by zero) cannot be
represented by a numeric value.
...
=section **
On 11/26/2002 8:02 AM, James Mastros wrote:
Guys, can we please not argue over just how arithmetic and such works
for NaN and Inf, and defer to IEEE specs (IEEE-754, AKA IEEE floating
point)? It'll save much argument, and that's how it'll almost
certianly be implemented anyway. Give examples
From: Bryan C. Warnock [mailto:[EMAIL PROTECTED]]
>
> If you don't already know whether it exists, or how it will
> roughly work (lexically), you shouldn't be discussing it on
> p6d. Kicked back to p6l.
[...]
> and again... what's the scope of p6d
p6d exists to document the language. A task whi
James Mastros wrote:
> On 11/17/2002 1:11 AM, Dave Storrs wrote:
> > Arrays know how to manage their own size; they will grow
> > and shrink as needed when you add or remove elements. You
> > never need to worry about whether an array has enough space
> > to hold the number of elements you are ab
On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
> (2) The behavior of an explicit bool type, _if_ one exists,
> that stores "truth", not "value". Such that C = (0 but true)> stores true, not 0, and does so in "the
> most efficient way".
There is no explicit bool type.
Larry Wall wrote:
>
>
James Mastros wrote:
>
> Guys, can we please not argue over just how arithmetic
> and such works for NaN and Inf, and defer to IEEE specs
> (IEEE-754, AKA IEEE floating point)? It'll save much
> argument, and that's how it'll almost certianly be
> implemented anyway.
NaN requires a pragma. As su
On Mon, Nov 25, 2002 at 09:01:36AM -0800, Michael Lazzaro wrote:
> (Umm... what's a better name than "coloned form"? That term sounds
> really... um... bad.)
How about:
- explicit radix
- dotted notation
- DSD (Dot Separated Digits)
--Dks
Nicholas Clark wrote:
But I was envisaging for ARM that r12 or r14 ought to be the scratch
register. The way the ABI works, with r12 trashed on function call entry,
but r0 used to return values from functions means that r12 is available
within an op, while mapping r0 to a parrot register for the
On Monday, November 25, 2002, at 11:23 PM, Joseph F. Ryan wrote:
(1) String Interpolation. This was pretty well spelled out by A2, so
there shouldn't be much to do except write it up, unless we want to
make any additional requests. There's some issues that need to be
finalized wrt Unicode,
On Tuesday, November 26, 2002, at 05:02 AM, James Mastros wrote:
Guys, can we please not argue over just how arithmetic and such works
for NaN and Inf, and defer to IEEE specs (IEEE-754, AKA IEEE floating
Yes and no. perl6-internals has been discussing this, so I think we
can pause and not w
On Tuesday, November 26, 2002, at 07:21 AM, Garrett Goebel wrote:
NaN requires a pragma. As such, shouldn't documenting it be deferred
till later?
Yes, but not _too_ much later. If C isn't the default behavior,
we have to document what _is_ the default behavior. :-) And if you
need a prag
On Tue, Nov 26, 2002 at 08:38:55AM -0600, Garrett Goebel wrote:
: James Mastros wrote:
: > On 11/17/2002 1:11 AM, Dave Storrs wrote:
: > > Arrays know how to manage their own size; they will grow
: > > and shrink as needed when you add or remove elements. You
: > > never need to worry about wheth
On Mon, Nov 25, 2002 at 10:06:13AM -0800, Michael Lazzaro wrote:
: With clarifications, and additional syntactic edge cases.
:
: The last remaining known "numeric literals" issue is whether we want to
: allow '.' in explicit radix, e.g. 10#1.234, or whether we want to
: disallow it as being Way
On Fri, Nov 22, 2002 at 05:49:58PM +, Piers Cawley wrote:
> Dave Storrs <[EMAIL PROTECTED]> writes:
>
> > Ideally, there could even be a per-list switch and a global switch
> > that says "(don't) show unique ids when interpolating lists/arrays".
> > By default, it gets set to "show", but it ca
On Mon, Nov 25, 2002 at 02:27:36PM -0800, Randal L. Schwartz wrote:
: > "Simon" == Simon Cozens <[EMAIL PROTECTED]> writes:
:
: Simon> What were the good reasons for not allowing localized lexicals in Perl 5?
:
: Nobody could explain it in 50 words or less.
:
: "What the hell is 'local my $f
On Tue, Nov 26, 2002 at 08:52:52AM -0600, Garrett Goebel wrote:
: On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
: > (2) The behavior of an explicit bool type, _if_ one exists,
: > that stores "truth", not "value". Such that C = (0 but true)> stores true, not 0, and does so in "the
: > most
On Mon, Nov 25, 2002 at 07:46:57PM -0500, Bryan C. Warnock wrote:
: Should an explicit bool type be part of the language? If so, how should
: it work? C storing only a truth property but
: no value makes little sense in the context of the larger language. So
: does handling truth as something oth
On Monday, November 25, 2002, at 04:46 PM, Bryan C. Warnock wrote:
On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
(2) The behavior of an explicit bool type, _if_ one exists, that
stores "truth", not "value". Such that C
stores true, not 0, and does so in "the most efficient way".
If yo
On Tuesday, November 26, 2002, at 09:47 AM, Larry Wall wrote:
: > (3) Context. How to determine it, how to force it. Hypothesis:
There
: > is a one-to-one relationship between Type and Context, such that
there
: > is a context that matches every type, and a type that matches every
: > contex
Nicholas Clark wrote:
(do all the unsigned with masks)
Yep
And we ought to make a generic "safe" version of the code for signed
truncation that works for platforms that are any or all of the following
holds
I tried this one:
inline op conv_i1(inout INT) {
#if 1
INTVAL x = $1;
x <<=
Gopal V wrote:
inline op conv_u1_ovf(inout INT) {
- if($1 >= 0 && $1 <= 256 ) {
+ if($1 >= 0 && $1 <= 255 ) {
Thanks, applied
leo
Larry Wall writes:
> Note that the "true" property is not the same as the "true" function.
> This tells me that properties may need their own namespace distinct
> from either subs or classes. (We've talked about defining properties
> as subs or classes, but either way is problematic. If we ha
"Larry Wall" <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 25, 2002 at 07:46:57PM -0500, Bryan C. Warnock wrote:
> : Should an explicit bool type be part of the language? If so, how should
> : it work? C storing only a truth property but
> : no value makes little sense in the context of the larger lang
On Tuesday, November 26, 2002, at 12:47 PM, Dave Whipp wrote:
I writing these definitions, I came to the conclusion that a
context is more than a type. Others may disagree.
Hmm, I suppose it depends on how broadly we use the term "type"; I like
your definition, if I understand it correctly. :
"Michael Lazzaro" <[EMAIL PROTECTED]> wrote
> I'm trying to think of a counterexample, in which you have a context
> that _cannot_ be represented as a "type" according to this very broad
> definition. I don't think it should be possible, is it? If it _is_
> possible, does that represent a flaw/li
On Tue, 2002-11-26 at 09:17, Garrett Goebel wrote:
>
> p6d exists to document the language. A task which consists of going over the
> A&E's and Larry's posts to p6l, etc. and flushing them out into
> deliverables:
>
> o Perl6/Parrot regression tests
> o Language Specification derived from tests
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.
> one until the more dedicated members st
On Tue, 2002-11-26 at 11:55, Michael Lazzaro wrote:
> Does it overflow (via an exception?), silently truncate, or ?. (Parrot
> may offer us both options.) We can choose to call the result "platform
> dependent", or define it explicitly. But let's wait and see what the
> Parrot people think, s
34 matches
Mail list logo
