Author: chromatic
Date: Mon Apr 16 23:27:57 2007
New Revision: 18254
Modified:
trunk/docs/pdds/pdd15_objects.pod
Changes in other areas also in this revision:
Modified:
trunk/src/pmc/class.pmc
trunk/t/oo/composition.t
trunk/t/oo/metamodel.t
trunk/t/oo/mro-c3.t
trunk/t/pmc/class.
Hi,
[08:07] <@particle> hrmm i think i have splint on my laptop
[08:08] <@particle> so i can probably test it on win32/msvc
[09:10] <@particle> the splint target uses sed? oh, we've got some work
do do
[09:14] < Infinoid> I've been using a little perlscript to remove
source filenames from the list
In January 2006, the paragraphs marked XXX below were added to docs/
configuration.pod concerning methods to be defined in the package for
each configuration step (e.g., config/init/manifest.pm for step
init::manifest)
=item C # starting at trunk, line 138
Returns a list of the names of an
In lib/Parrot/Configure.pm there is the following code (trunk:
starting at line 254):
# XXX cc_build uses this verbose setting, why?
$self->data->set( verbose => $verbose ) if $n > 2;
$n is the index in the array of configuration steps of the step
currently being processed. $verbos
On Monday 16 April 2007 16:58, [EMAIL PROTECTED] wrote:
> + obj_guts = mem_sys_allocate_zeroed(sizeof(Parrot_Object));
The mem_allocate_typed and mem_allocate_zeroed_typed macros make this slightly
nicer (and C++ compiler safe too):
obj_guts = mem_allocate_zeroed_typed(Parrot_Obj
Of the things I was hoping would be sorted out before release...
Jonathan Worthington wrote:
* addattribute segfaults if passed a PDD15 class. I'll fix that
tomorrow, if nobody beats me to it
Done by chromatic++. :-)
* Oh, and the Role PMC doesn't do the name/namespace stuff right yet;
it's m
Jonathan Worthington wrote:
What should happen: Class manufactures an object and init and init_pmc
of Object both throw exceptions. That means creating a new Object PMC
in the new method of Class using pmc_new_noinit (IIRC) and setting up
its guts from within Class.
Implemented this now, and in
# New Ticket Created by "Yehoshua Sapir"
# Please include the string: [perl #42558]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42558 >
Without this patch, for runtime/parrot/library/config.pir to work, parrot
has to be
Hi, I have updated the pkgsrc package of parrot to the latest 0.4.10 (I hope
to maintain the following releases too), There's an ancient patch into the
package to fix the build on dragonflybsd. I have no dflybsd but it looks ok
for me.
Keep up the good work!
--pancake
# cat patches/patch-aa
$Ne
Andy Dougherty wrote:
Are you *sure* it's been fixed? My test involved running a simple
program something like this
.sub _main
.local pmc pmc1
pmc1 = new ResizableBooleanArray
pmc1[1000] = 1
.end
and incrementing the '1000'. I found that for every element I ad
chromatic wrote:
On Sunday 15 April 2007 15:52, Jonathan Worthington wrote:
Sorry, I didn't get to adding one yet, but this should do it:
$P0 = new 'Class'
addattribute $P0 'foo'
Hm, it segfaults for me (and rightly so) if I instantiate a non-class
(try 'Hash' for some fun), but when
Alek Storm (via RT) wrote:
The following code demonstrates the reversed output of Object.can():
...
I've attached a patch to fix this.
Applied in r18239.
Thanks!
Jonathan
On Apr 16, 2007, at 8:46 AM, Andy Dougherty wrote:
On Sun, 15 Apr 2007, Allison Randal via RT wrote:
According to our records, your request regarding
"[TODO] ResizableBooleanArray uses 64 bytes per bit of information"
has been resolved.
If you have any further questions or concerns, please
On Apr 16, 2007, at 8:46 AM, Andy Dougherty wrote:
On Sun, 15 Apr 2007, Allison Randal via RT wrote:
According to our records, your request regarding
"[TODO] ResizableBooleanArray uses 64 bytes per bit of information"
has been resolved.
If you have any further questions or concerns, please
With the next release roughly a day away, please refrain from making
any major changes in trunk. If you have major changes, hold on to
them, create a branch, or create a [PATCH] ticket. Generally, just
keep the release in mind while making any commits.
Any bug fixes or changes to HLLs or document
Author: larry
Date: Mon Apr 16 09:59:02 2007
New Revision: 14375
Modified:
doc/trunk/design/syn/S11.pod
Log:
Module names must respect case sensitivity even on case-insensitive systems.
Modified: doc/trunk/design/syn/S11.pod
===
HaloO,
Jonathan Lang wrote:
But then, a file handle doesn't behave exactly
like "standard in" or "standard out", either (last I checked, Perl 5
won't do anything useful if you say "seek STDIN, 0, SEEK_END").
How should Perl 6 behave? I guess it's possible to return a
lazy list that captures ST
HaloO,
Uri Guttman wrote:
[..] if
dirs mapped well onto file handles they would have been mapped that way
long ago in the OS. in 30+ years that hasn't happened afaik.
Hans Reiser is promoting just the unification of files and
directories in his Reiser4 filesystem. In particular does
it support
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #42554]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42554 >
I went to check on a follow-up message I received today:
[perl #39063] [RESOLVED]
On 16 Apr 2007 13:00:27 -
Parrot Bug Summary <[EMAIL PROTECTED]> wrote:
> 41858 [CAGE] Make a reasonable set of rules for splint
Hi,
Random cage cleaner here. At Andy Lester's suggestion, I've begun
working on this splint stuff. So everything below is all his fault. :)
I found that "make s
On Sun, 15 Apr 2007, Allison Randal via RT wrote:
> According to our records, your request regarding
> "[TODO] ResizableBooleanArray uses 64 bytes per bit of information"
> has been resolved.
>
> If you have any further questions or concerns, please respond to this message.
>
> For other to
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Apr 16 13:00:02 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
A. Pagaltzis wrote:
Does it mean that basically the assertion is a character/string
property instead of the character/string itself?
No, it is a zero-width assertion. `at(1)` means the position
“between” the 0th and 1th character of the string.
I see thank you
Also, what is the correct way
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #42548]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42548 >
The following code demonstrates the reversed output of Object.can():
.sub main :main
$
Alek Storm (via RT) wrote:
The following code causes a segfault:
.sub main :main
$P0 = new "Object"
$P0.'foo'()
.end
This is because the vtable methods in Object assume a valid pointer to
the object's internal representation, which is only initialized in
init_pmc.
That probably has to chang
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #42547]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42547 >
The following code causes a segfault:
.sub main :main
$P0 = new "Object"
$P0.'foo'()
26 matches
Mail list logo
