I've just built the 5/2/2008 snapshot of GCC 4.4 and Parrot builds
fine on it. I wonder what new warning flags 4.4 has that I can exploit.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Thu Dec 13 05:54:17 2007, kjs wrote:
> On Tue Jun 14 02:30:00 2005, chip wrote:
> > It makes sense to allow e.g. C<$P0 = add $P1, $P2> as alternative
> > syntax for C. However, when the first parameter is
> > "inout" rather than "out", assignment syntax is *not* appropriate.
> >
> > For exampl
On Thu, May 8, 2008 at 9:55 PM, chromatic <[EMAIL PROTECTED]> wrote:
> Your null-checking patch will work, but I don't want to add more checking to
> parrot_mark_hash() right now, as it's already full of special cases. Here's
> my inclination.
Looks good to me. I see you also get rid ot the v
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
It's called overload resolution. Perl 6 can't do
that at compile time unless *all* targets are
available as rw and readonly variants.
I don't follow that statement. Can you give an example?
On Thursday 08 May 2008 11:09:52 chromatic wrote:
> That to me seems like the real problem. Did anyone experiment with using
> hash_delete?
>
> > The problem can be fixed by checking in parrot_mark_hash that the key
> > is no null before calling pobject_lives. The attached path does it.
>
> That
While reading through actions.pm I found that method scope_declarator
wasn't very readable because it was very long.
A big part of that is the declaration of attributes which needs some
special handling.
The attached patch moves that code to a separate function called
declare_attribute. It doesn'
On Thursday 08 May 2008 04:39:57 NotFound wrote:
> Last night in #parrot particle informed of a bug in a msvc++ build. By
> his suggestion, me and others were able to reproduce it in other
> platforms by using the gcdebug core:
>
> ./parrot --runcore=gcdebug t/pmc/orderedhash_9.pasm
>
> Looks like
HaloO,
Larry Wall wrote:
.WHAT gives you an value
of undef that happens to be typed the same as the object in $x,
presuming your metaobject believes in types.
Why does the metaobject have to believe in types? I think it
suffices to define that .WHAT returns a unique binding in the
scope of int
# New Ticket Created by NotFound
# Please include the string: [perl #53890]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53890 >
Last night in #parrot particle informed of a bug in a msvc++ build. By
his suggestion, me an
Sorry, forgot to attach the patch file.
--
Salu2
Index: src/pmc/class.pmc
===
--- src/pmc/class.pmc (revisión: 27379)
+++ src/pmc/class.pmc (copia de trabajo)
@@ -644,8 +644,11 @@
/* If we already have an attribute of thi
# New Ticket Created by NotFound
# Please include the string: [perl #53850]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53850 >
Hello.
The attached patch adds the class name to the exception attribute
already exists in
HaloO,
John M. Dlugosz wrote:
- const int& is preferred over int/int&.
- const int* is preferred over int*.
You mean when in each case both versions are
defined as overloads only the preferred ones
are ever called? C++ is the other way around.
For an int* argument the int* version is preferred
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #53896]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53896 >
On Wed, May 07, 2008 at 11:34:07AM -0400, brian d foy via RT wrote:
> Ticket http
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
Coming back to how C++ handles static overloading. How is
the sort order of (int *), (int &), (int), (const int *),
(const int &), (const int), (int * const) and (const int * const)?
I'm too lazy to look up the details, sorry.
Without looking a
N.B. "flak" and "flack" are two different words, the latter referring
to a political position.
On 5/8/08, John M. Dlugosz <[EMAIL PROTECTED]> wrote:
> TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
>>> When I mentioned this before, there was big flack over mentioning the
>>> way C++ did it. I
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
When I mentioned this before, there was big flack over mentioning the
way C++ did it. I think that must have been miscommunicated, since I
wasn't even talking about summing all the arguments when he brought
up "Manhattan dispatch".
BTW, what
On May 7, 2008, at 10:35 PM, Geoffrey Broadwell via RT wrote:
On Wed, 2008-05-07 at 18:22 -0700, James Keenan via RT wrote:
On Sun Apr 20 19:01:44 2008, [EMAIL PROTECTED] wrote:
I would like to propose both short-term and long-term remedies.
Short-term: If you are proposing a new configurat
HaloO,
Nicholas Clark wrote:
Is there any way to pre-declare that I want to defer baking the role from a
class? (Which I guess would make it an error to reference that role at run
time in any way, until I'd issued a second declaration that I was done, and
baking season is open)
I fear this is
Hello,
I want you to offer to replace the broken link
"http://parrot.homelinux.org/packages"; to
"ftp://ftp.uni-siegen.de/pub/parrot.rpms/fedora";.
The link I think of is on the WWW-page
"http://www.parrotcode.org/source.html";.
You can klick there under the topic "Packages" at the link "FedoraCo
On Wednesday 07 May 2008 19:35:03 Geoffrey Broadwell wrote:
> On Wed, 2008-05-07 at 18:22 -0700, James Keenan via RT wrote:
> > > Long-term: We need a Parrot design document on configuration. Such
> > > a document should cover what configuration is, why we have decided to
> > > include the conf
20 matches
Mail list logo
