I just launched the Security PDD out of draft
(docs/pdds/pdd18_security.pod). Please take a moment to read through it
and comment. It's more about high-level concepts than low-level
implementation details. In some areas it's quite radical, and in others
merely represents what's currently recogn
Author: allison
Date: Sat Mar 1 22:27:20 2008
New Revision: 26179
Added:
trunk/docs/pdds/pdd18_security.pod
- copied unchanged from r26178, /trunk/docs/pdds/draft/pdd18_security.pod
Removed:
trunk/docs/pdds/draft/pdd18_security.pod
Changes in other areas also in this revision:
Modifi
Author: allison
Date: Sat Mar 1 22:23:29 2008
New Revision: 26178
Modified:
trunk/docs/pdds/draft/pdd18_security.pod
Log:
[pdd] Rewritten Security PDD.
Modified: trunk/docs/pdds/draft/pdd18_security.pod
==
--- trunk
r26053 produces the segfault shown below, which looks like another
case of trying to compare the HLL name "lisp" to something corrupted
from the HLL name-to-ID hash. (FWIW, it was still broken as of r26165.)
However, if I revert the src/pmc/string.pmc change, it works again,
and also in r26
# from chromatic
# on Saturday 01 March 2008 17:19:
>Will Coleda and Dave Rolsky are currently performing similar features
> for Parrot; either of them might be a good first choice.
>
>If neither can do it, I will.
Excellent, thanks. Parrot seems to be nicely supplied with soc managers
now! Je
The attached patch fixes some pdump bugs and deficiencies, and adds
symbolic display of object flag bits. Does anybody mind if I make pdump
more verbose in this way? Any suggestions for how to get symbolic flag
names without duplicating the C definition here?
TIA,
On Sat Mar 01 04:18:38 2008, bernhard wrote:
> Hi,
>
> with r26143 t/perl/Parrot_Test.t is failing for me.
> Somewhat related might be that t/compilers/imcc/syn/errors.t, RT#51280,
> is working for me.
> I'm stumped.
>
>
Can you svn up, re-Configure, and re-make, and then try these tests again
Matt: I applied your patch in r26162. Can you make certain it works
with a pre-0.64 version of Test::Builder (such as we formerly had in the
Parrot distro)?
We'll also have to see if this resolves the problems reported by Barney
in http://rt.perl.org/rt3/Ticket/Display.html?id=51308
kid51
On Fri Feb 29 23:20:07 2008, kraai wrote:
> Howdy,
>
> The failure tests in t/perl/Parrot_Test.t fail because the file name
> and line number format used by Test::Builder on my system differs from
> that expected. That is, the test suite expects
>
> # at $0 line $line.
>
> whereas
>
> #
Patch applied to trunk in r26145.
10 matches
Mail list logo