-- From http://rakudo.org/parrot/index.cgi?bug_day_2007_04_14 --
Bug Day
On Saturday, 14 April 2007, please join us on IRC in #parrot
(irc.perl.org) to work on closing out as many RT
(https://rt.perl.org/rt3/ ) tickets as possible in the parrot queue.
This will help us get ready for the next re
On 4/11/07, Allison Randal <[EMAIL PROTECTED]> wrote:
> On 4/11/07, Bob Rogers < [EMAIL PROTECTED] > wrote:
>>I like this one, but I also have another alternative. First, make
all
>>class-modification code (add_method, remove_attribute, etc) return a
>>PMC*. Whenever one of these m
Nicholas Clark wrote:
On the other hand, we've managed very well in Perl 5 with the flag data in
embed.fnc and generating the annotated headers programmatically.
Interesting. I quite like this.
Nicholas Clark
Ron
On Apr 12, 2007, at 1:54 PM, Nicholas Clark wrote:
On Thu, Apr 12, 2007 at 01:50:09PM -0500, Joshua Isom wrote:
On Apr 12, 2007, at 9:29 AM, Nicholas Clark wrote:
My view of this is something along these lines. You can use any
function you want at all, but if it's not documented as part o
On 4/12/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
On Thu, Apr 12, 2007 at 01:50:09PM -0500, Joshua Isom wrote:
>
> On Apr 12, 2007, at 9:29 AM, Nicholas Clark wrote:
> My view of this is something along these lines. You can use any
> function you want at all, but if it's not documented as p
On Thu, Apr 12, 2007 at 01:50:09PM -0500, Joshua Isom wrote:
>
> On Apr 12, 2007, at 9:29 AM, Nicholas Clark wrote:
> My view of this is something along these lines. You can use any
> function you want at all, but if it's not documented as part of the
> supported API, there's nothing saying I
On Apr 12, 2007, at 9:29 AM, Nicholas Clark wrote:
On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote:
On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
I think that we need to tread very carefully with adding additional
gcc-isms to Parrot, lest we break compatibility wi
# New Ticket Created by Steve Peters
# Please include the string: [perl #42475]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42475 >
-ansi -pedantic choke on the call to asm() in src/ops/core.ops. This is
because asm() i
# New Ticket Created by Steve Peters
# Please include the string: [perl #42474]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42474 >
Unlike Perl lists, commas are not allowed to be dangling in enum lists. The
attached pa
Nicholas Clark wrote:
On Thu, Apr 12, 2007 at 04:56:15PM +0200, [EMAIL PROTECTED] wrote:
On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote:
On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
While poking the GCC documentation I found that there's a feature
available to li
On 4/12/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> -# If we are building shared, need to include dynamic
>> libparrot.lib, otherwise
>> +
>> +# If we are building shared, need to include dynamic
>> parrot.lib, otherwise
>> # the static libparrot.lib.
> this code secti
On Thu, Apr 12, 2007 at 04:56:15PM +0200, [EMAIL PROTECTED] wrote:
> On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote:
> > On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
> > > While poking the GCC documentation I found that there's a feature
> > > available to limit the
On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote:
> On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
> > While poking the GCC documentation I found that there's a feature
> > available to limit the exported symbols (with GCC >= 3.3). Maybe worth
> > considering?
> > It's
jerry gay wrote:
On 4/12/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Attached is a proposed patch to change the libparrot names and locations
for Windows. I have tested the changes for "core" Parrot on Win32
Visual C++, Cygwin GCC, MinGW GCC and Ubuntu GCC.
this looks fabulous. thank you f
On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote:
> On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
> > While poking the GCC documentation I found that there's a feature
> > available to limit the exported symbols (with GCC >= 3.3). Maybe worth
> > considering?
> > It's
On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
> While poking the GCC documentation I found that there's a feature
> available to limit the exported symbols (with GCC >= 3.3). Maybe worth
> considering?
> It's probably a design decision. If there's an option to limit the
> expor
On 4/12/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Attached is a proposed patch to change the libparrot names and locations
for Windows. I have tested the changes for "core" Parrot on Win32
Visual C++, Cygwin GCC, MinGW GCC and Ubuntu GCC.
this looks fabulous. thank you for providing your
While poking the GCC documentation I found that there's a feature
available to limit the exported symbols (with GCC >= 3.3). Maybe worth
considering?
It's probably a design decision. If there's an option to limit the
exported symbols or make all available, which one should be taken?
http://g
Attached is a proposed patch to change the libparrot names and locations
for Windows. I have tested the changes for "core" Parrot on Win32
Visual C++, Cygwin GCC, MinGW GCC and Ubuntu GCC.
Minor Changes
-
* libparrot_(static|shared) now contains the path to the library, not
the l
19 matches
Mail list logo
