Re: [perl #30613] [PATCH] Parrot m4 0.0.7
Bernhard Schmalhofer [EMAIL PROTECTED] wrote: this is just a minor update of Parrot m4. There are no new features. Thanks, applied. leo
Re: Python::Bytecode
Leopold Toetsch wrote: ... is on CPAN (said Dan) and is broken. I'd be glad if people could fix it and send me a running version ;) * constants are messed up * it doesn't disassemble all code objects of a .pbc - just one If you could give me a bit more to go on, I'd be willing to give this a shot. I don't know much about byetcode, but I'd love to save Dan from a pie in the face (from what I gather he's had a rough go of it lately). Maybe you could give me an example of some input and the correct output? Or some documentation? I've checked out parrot and installed Python::Bytecode, so let me know what I can do to help out. matt
Re: Phalanx: What if full coverage isn't possible?
Michael G Schwern wrote: Test coverage is a useful *heuristic* for test effectiveness. Like all heuristics if you push it too far it falls apart. Get as close to 100% as is useful and don't worry about the rest. Indeed. Brian Marick wrote a great paper on this topic - How to Misuse Code Coverage, http://testing.com/writings/coverage.pdf. -- Danny R. Faught Tejas Software Consulting http://tejasconsulting.com/
Re: [perl #30557] [BUG] Re: cvs commit: parrot/config/init data.pl
On Thu, Jul 01, 2004 at 09:20:22AM -0700, Dennis Rieks wrote: perl Configure.pl --icuheaders=/devel/tinder/vc6/icu/include --icushared=/libpath:/devel/tinder/vc6/icu/lib icuuc.lib Generating build filesdone. Moving platform files into place..done. Recording configuration data for later retrieval..Can't locate object method Sortkeys via package Data::Dumper; (perhaps you forgot to load Data::Dumper;?) at config/init/data.pl line 212, IN line 23. --8--- Another problem with make: (I think this depends on the first problem.) --8--- About to run build command: nmake Microsoft (R) Program Maintenance Utility Version 6.00.9782.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. Compiling with: xx.c cl -nologo -MD -Zi -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -Zi -I./include -I/devel/tinder/vc6/icu/include -DHAS_JIT -DI386 xx.obj -c xx.c C:\Perl\bin\perl.exe build_tools\vtable_h.pl C:\Perl\bin\perl.exe build_tools\ops2pm.pl ops/core.ops ops/bit.ops ops/cmp.ops ops/debug.ops ops/dotgnu.ops ops/experimental.ops ops/io.ops ops/math.ops ops/object.ops ops/pmc.ops ops/rx.ops ops/set.ops ops/stack.ops ops/string.ops ops/sys.ops ops/var.ops No 'VERSION = ...;' line found before beginning of ops in file 'ops/core.ops'! NMAKE : fatal error U1077: 'C:\Perl\bin\perl.exe' : return code '0xff' Stop. nmake complete Any ideas? Only sort keys if supportet? My mistake here has been fixed now (I think by Jürgen Bömmels) - yes, only sort keys if supported. Does this resolve your other problem? Nicholas Clark
native_pbc fixes
Here are regenerated number_?.pbc files for the t/native_pbc/number.t,
plus a couple of tweaks I found on the way in Tru64 and IRIX/64.
I still have test failures in both those two and in IRIX there a is a
lot of fun getting the compiler selected right (even in 64-bit IRIX
there are both 32 and 64-bit compilers and object files, pain...) but
I managed to get parrot to link and to generate the pbc files. No time
to resolve those failures now, I am afraid.
Also, to generate the number_2.pbc I had to compile a new uselongdouble
Perl in Linux and in there I had to #if 0 the below in src/platform.c to
get parrot linked, both those asserts were failing at some point or another.
static void*
Parrot_memcpy_aligned_mmx_debug(void* d, void* s, size_t l)
{
assert( (l 0xf) == 0);
#if 0
assert( ((unsigned long) d 7) == 0);
assert( ((unsigned long) s 7) == 0);
#endif
return
((Parrot_memcpy_aligned_mmx_t)(Parrot_memcpy_aligned_mmx_code))(d, s, l);
}
Quite a lot of failures from this longdouble parrot (no wonder, after
disabling two asserts), but at least it was able to generate a pbc that
the other platforms are able to understand. The box has an AMD Duron,
that's about all I know about it.
--
Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special
biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
nat.tgz
Description: GNU Zip compressed data
Looking for module dependency information
To whom it may concern, I am looking for information on CPAN module dependencies. Specifically, does somebody maintain and regularly update such a list? The reason is that I would like to integreate this with testing information from the CPAN Testers. So if I find that there are no testing results for platform 'x' for a specific module, I can check to see if one of the dependent modules fail on that platform. Thanks, Robert Rothenberg (FYI, I've just posted a question on PerlMonks regarding this, http://www.perlmonks.org/index.pl?node_id=373386)
Re: The .bytes/.codepoints/.graphemes methods
Austin Hastings [EMAIL PROTECTED] writes:
I think this is something that we'll want as a mode, a la
case-insensitivity. Think of it as mark insensitivity.
Makes sense to me, but...
Maybe it can just roll into :i?
It will probably get used in _conjunction_ with case-insensitivity
quite a lot, but I suspect people will want to be able to use one
without the other.
Since mark-insensitivity is probably mostly a non-issue in the ASCII
world, it would probably be a better candidate than average for being
turned on using a unicode character, if we're running low on letters
for designating these rules.
--
$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b-()}}
split//,[EMAIL PROTECTED]/ --;$\=$ ;- ();print$/
Re: Looking for module dependency information
On Sat, Jul 10, 2004 at 03:35:52PM -0400, Robert Rothenberg wrote: I am looking for information on CPAN module dependencies. Specifically, does somebody maintain and regularly update such a list? The reason is that I would like to integreate this with testing information from the CPAN Testers. So if I find that there are no testing results for platform 'x' for a specific module, I can check to see if one of the dependent modules fail on that platform. Most modules now have a META.yml file which contains (amongst other things) module dependency information. Simplest thing to do would be to make a local miniCPAN mirror [1] and walk through the archive files [2] in modules/02packages.details.txt looking for META.yml. [1] http://www.stonehenge.com/merlyn/LinuxMag/col42.html [2] Archive::Any will come in handy -- Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/ the chair. it wants to die. oh no! she sees me! she attacks!
Re: The .bytes/.codepoints/.graphemes methods
Jonadab the Unsightly One writes: Austin Hastings [EMAIL PROTECTED] writes: I think this is something that we'll want as a mode, a la case-insensitivity. Think of it as mark insensitivity. Makes sense to me, but... Maybe it can just roll into :i? It will probably get used in _conjunction_ with case-insensitivity quite a lot, but I suspect people will want to be able to use one without the other. Since mark-insensitivity is probably mostly a non-issue in the ASCII world, it would probably be a better candidate than average for being turned on using a unicode character, if we're running low on letters for designating these rules. Or, god forbid, a word? m:base/que mas/ We're not mathematicians: we're allowed to use more than one letter in a row to designate something :-) Luke
