[perl #50938] [PATCH] Remove instantiate opcode

Patch applied in r25869. Closing ticket.

[perl #42375] [DEPRECATED] pmcinfo op

Applied a modified version of the patch in r25767. Closing ticket.

[perl #48142] [DEPRECATED] class_type vtable

Patch applied in r25765. Closing ticket.

[perl #50066] [BUG] $LIBPARROT_STATIC macro not expanded properly when building pbc_to_exe

Andy's patch applied in r25763. This corrects the issue. Closing the ticket.

[perl #48024] [DEPRECATED] type ids

Completed as per r25053.

[perl #42375] [TODO] deprecate pmcinfo op

On Sat Jan 12 04:42:26 2008, allison wrote: > This opcode has been superseded by 'inspect'. The pmcinfo opcode is removed by the attached patch. I would have committed this directly however, I'm not 100% sure that removing the: 'Class PMCs also have the "I am a class" flag set on them.' test was

[perl #48142] [DEPRECATED] class_type vtable

On Tue Dec 04 20:12:24 2007, coke wrote: > From PDD17: > > =item class_type > >INTVAL class_type(INTERP, PMC* self) > > Return the integer type of the PMC. [NOTE: will be deprecated when type > IDs are deprecated.] The attached patch removes this vtable entry. The only thing still which s

[perl #48266] [TODO] [C] Write file-level documentation

Apologies for the extra email! This was an abortive attempt to Ctrl-C out of a command line RT session. Closing ticket.

[perl #46697] [TODO] [C] Move the exception macros from src/pmc/coroutine.pmc into exceptions.h

On Sun Nov 11 09:57:07 2007, coke wrote: > On Mon Oct 22 15:02:26 2007, rgrjr wrote: > > From: Paul Cochrane (via RT) <[EMAIL PROTECTED]> > >Date: Mon, 22 Oct 2007 10:43:32 -0700 > > > ># New Ticket Created by Paul Cochrane > ># P

[perl #41862] [CAGE] Make a reasonable set of rules for lint

On Thu Mar 15 19:42:17 2007, ptc wrote: > Andy has a pretty decent set of rules for perl5's code in that > project's Makefile. Take a look at those for a start. Andy Lester put a large chunk of effort into the options for both Sun lint and BSD lint. After adding some extra flags to BSD lint (r2

[perl #46007] [CAGE] licensing cleanup

On Tue Oct 02 13:39:30 2007, [EMAIL PROTECTED] wrote: > Parrot is no longer licensed under the GPL directly (though it is > available under the GPL through the Artistic 2.0). Update or remove > references to the GPL license in these files: > > debian/copyright:45 Removed mention of some no-long

[perl #41858] [CAGE] Make a reasonable set of rules for splint

On Sun Oct 21 13:25:50 2007, ptc wrote: > On Thu Mar 15 19:12:48 2007, ptc wrote: > > splint spews many many errors by default. Take a look at the > > Makefile that perl5 has for the start of some rules that Andy worked > > on for the perl5 code. > > Andy Lester has done a very large amount of wo

[perl #41858] [CAGE] Make a reasonable set of rules for splint

On Thu Mar 15 19:12:48 2007, ptc wrote: > splint spews many many errors by default. Take a look at the > Makefile that perl5 has for the start of some rules that Andy worked > on for the perl5 code. Andy Lester has done a very large amount of work on this, and a very good set of rules for splint

[perl #41886] [CAGE] Use lcov to show code coverage

On Mon Mar 19 09:54:26 2007, ptc wrote: > On Sat Mar 17 14:19:51 2007, ptc wrote: > > The lcov tool from the Linux Test Project > > (http://ltp.sourceforge.net/coverage/lcov.readme.php) can be used to > > produce html output of code coverage information (I believe this looks > > similar to Devel::

[perl #46595] [PATCH] a few spelling fixes

Patch applied in r22363. Thanks!

[perl #38844] [TODO] Make lint, splint and tags targets

On Tue Jul 10 05:08:19 2007, ptc wrote: > Just updating this ticket to the current state of play: > > > The lint target needs to be renamed to splint. > > Actually, this has been changed to sunlint and bsdlint. The splint > target has existed for a while (in two forms; now combined as of r1972

[perl #40392] [CAGE] convert C to C

The only files which still have this issue outstanding are[1]: src/jit/ppc/jit_emit.h src/jit/alpha/jit_emit.h src/jit/hppa/jit_emit.h src/jit/mips/jit_emit.h src/jit/sun4/jit_emit.h Attached are patches for these files as I am unable to test on these platforms (diff-ed agains r22293).

[perl #43661] [CAGE] Get parrot configuration to autodiscover gcc warning flags

James, Thanks for pointing out what you meant. I think I must have been having a bit of a brain-fade moment or something... On Sun Jul 08 18:06:03 2007, [EMAIL PROTECTED] wrote: > Paul Cochrane wrote: >Perl 5 is able to work out > > automatically the warnings flags of gcc and then use those

[perl #38969] [CAGE] parrot source does not conform to standards

> http://rt.perl.org/rt3/Ticket/Display.html?id=39824 Since the above ticket has now been resolved, does this mean that this ticket can also be resolved? Paul

[perl #39824] [CAGE] tools/dev/check_source_standards.pl -- this should be a test

On Fri Nov 17 14:17:18 2006, particle wrote: > ~ all but one test have been adapted for and moved to t/codingstd/ > ~ remaining test is for not-yet-approved codingstd item The remaining test complains about more than one '.' in a filename and filenames which don't conform to the 8.3 format. My f

[perl #43661] [CAGE] Get parrot configuration to autodiscover gcc warning flags

On Sun Jul 08 15:09:19 2007, ptc wrote: > At present we have to specify warnings flags for each version of gcc > (see config/auto/gcc.pm). This is a pain. Perl 5 is able to work out > automatically the warnings flags of gcc and then use those for > compilation. Parrot should do this too. Automa

[perl #39760] [CAGE] make warnings (r13197 - x86-msvc-7.1)

On Sat Jul 15 14:47:48 2006, rblasch wrote: > Jerry Gay (via RT) wrote: > > # New Ticket Created by Jerry Gay > > # Please include the string: [perl #39760] > > # in the subject line of all future correspondence about this issue. > > # http://rt.perl.org/rt3/Ticket/Display.html?id=39760 > > >

[perl #46223] [PATCH] Remove dead code in src/pmc/pair.pmc (Coverity CID 5)

On Mon Oct 08 12:14:07 2007, leo wrote: > Am Montag, 8. Oktober 2007 19:05 schrieb Paul Cochrane: > > So, the patch is right (however, for my wrong reasoning)?  Is > everyone > > happy if I apply it then? > > $ svn ann src/pmc/pair.pmc > 8374leo A Pair PMC represents one key => value map

[perl #45915] [TODO] rethrow_c_exception() needs completion after exception implementation completed

On Mon Oct 01 14:36:55 2007, ptc wrote: > In src/exceptions.c there is mention about "exception being still in TODO". > This means that something about exceptions is not yet finished, and needs > to be implemented so that the code mentioned here (near > rethrow_c_exception()) can be completed. S

[perl #45907] [TODO] Get rid of internal_exceptions ??

This time I'm going to add some text to the ticket... For the umteenth time... src/exceptions.c has a todo comment in it: * XXX TODO get rid of all the internal_exceptions or call them * with an interpreter arg The fact that we can't completely get rid of internal_exception() has al

[perl #41783] [BUG?] main isn't in src/parrot.c

On Sat Mar 10 19:15:20 2007, coke wrote: > From docs/BROKEN.pod. > > > Is this something that needs fixing? > > (it's in compilers/imcc/main.c) There is also a src/main.c which says it is the entry point for to Parrot programs. Should src/parrot.c be removed?

[perl #45437] [BUG]: platform-specific utility 'sed' appears in makefile

On Thu Sep 13 22:39:32 2007, [EMAIL PROTECTED] wrote: > > On Sep 13, 2007, at 8:21 PM, Jerry Gay (via RT) wrote: > > > # New Ticket Created by Jerry Gay > > # Please include the string: [perl #45437] > > # in the subject line of all future correspondence about this issue. > > # http://rt.perl.o

[perl #45423] [PATCH] pdd22_io.pod formatting changes

Applied in r21262.

[perl #41168] graceful "no compiler" error message?

On Thu Sep 13 02:16:12 2007, ptc wrote: > > > Applied the patch with some modifications so that it runs > correctly on > > > Windows in r21212. Tested on Linux x86, Windows and Cygwin. > > > > But did you actually address any of my objections? For example, do > you > > now pay attention to exit c

[perl #45387] [BUG] languages/lua/pmc/lua_private.h generating error in t/codingstd/c_header_guards.t

kid51, This should be fixed as of r21207. ptc

[perl #41168] graceful "no compiler" error message?

On Wed Sep 12 06:00:56 2007, ptc wrote: > On Mon Mar 19 15:59:44 2007, [EMAIL PROTECTED] wrote: > > On Monday 19 March 2007 12:22, Andy Dougherty wrote: > > > > > I found the ticket that introduced this failing behavior, so I'm > resending > > > my message below with a fixed-up subject line to ent

[perl #41168] graceful "no compiler" error message?

On Mon Mar 19 15:59:44 2007, [EMAIL PROTECTED] wrote: > On Monday 19 March 2007 12:22, Andy Dougherty wrote: > > > I found the ticket that introduced this failing behavior, so I'm resending > > my message below with a fixed-up subject line to enter into RT. In brief, > > this patch incorrectly as

[perl #45281] [CAGE] Replace io->vtable->whatever with VTABLE_whatever(interp, io, ...)

On Sat Sep 08 14:11:57 2007, [EMAIL PROTECTED] wrote: > On Saturday 08 September 2007 14:00:39 Paul Cochrane via RT wrote: > > > Is this restricted to just the pmc's? C also found instances > > in: > > > > src/ops/io.ops > > src/hash.c > > src

[perl #45281] [CAGE] Replace io->vtable->whatever with VTABLE_whatever(interp, io, ...)

On Sat Sep 08 12:37:00 2007, [EMAIL PROTECTED] wrote: > Several PMCs use vtable methods directly, rather than going through the > accessor macros. These are particularly evident in bytecode freezing and > thawing. > > The existing code looks like: > > io->vtable->push_integer(INTERP,

[perl #39088] [CAGE] Add conditional GCC attributes to functions

On Fri May 05 15:18:22 2006, petdance wrote: > > GCC has a number of attributes that we can slap on functions. For > example, GCC's analysis of flow control will be greatly improved when > we put __attribute(noreturn)__ on real_exception(), to tell GCC that > it can't return, like exit(). >

[perl #38468] [TODO] modify copyright info in parrot repo

On Wed Feb 08 06:55:12 2006, [EMAIL PROTECTED] wrote: > ~ tests will be designed to detect differences between the official > copyright text (README) and text files in the repository, with an > exception list for files that do not contain the copyright message A new test along these lines has be

[perl #44469] Fix grammatical problems in docs/optable.pod

Thanks! Applied in r20535.

[perl #40865] [CAGE] ensure isxxx() and toxxx() are only passed unsigned char values

Since we now have tests covering this issue, and the instances in the code have been cleaned up, I'm now closing this ticket.

[perl #40865] [CAGE] ensure isxxx() and toxxx() are only passed unsigned char values

On Mon Nov 13 14:24:04 2006, chip wrote: > The C standard says that the isxxx() and toxxx() functions are only defined > if their input falls in the domain of unsigned char, or the special case of > -1 ("EOF"). Therefore, all input values to these functions should be cast > (directly or indirec

[perl #41860] [CAGE] Run Parrot under Coverity Prevent

Parrot is now running under Coverity Prevent. The address for access to its output is: http://scan2.coverity.com:9035/. If you wish to get an account to be able to then access the scan page, you will need to send an email to [EMAIL PROTECTED] I'm going to put this info up on the Parrot wiki

[perl #37015] [TODO] docs - svn howto

How does this file look? Does it explain everything which needs to be explained? If everything's ok (or noone makes any noise over the next few days) I'll add this file to docs/project. Comments most definitely welcome. Paul commiter_guide.pod Description: Binary data

[perl #43927] [PATCH] Typo in docs/art/pp003-oop.pod

Thanks! Applied as r19899.

[perl #40392] [CAGE] convert C to C

On Tue Jun 26 02:36:59 2007, ptc wrote: > On Thu Sep 21 14:38:40 2006, particle wrote: > > parrot's source is littered with internal_exception() calls, the bulk > > (all?) of which should be converted to real_exception() calls. > > internal exceptions are uncatchable, and might as well be called >

[perl #38844] [TODO] Make lint, splint and tags targets

Just updating this ticket to the current state of play: > The lint target needs to be renamed to splint. Actually, this has been changed to sunlint and bsdlint. The splint target has existed for a while (in two forms; now combined as of r19721 into the one target). > Then create a new lint ta

[perl #43613] remove 'compile' opcode

Resolved in r19716

[perl #43657] [PATCH] Grammatical error in docs/vtables.pod

Thanks again! Applied in r19703.

[perl #43659] [PATCH] typo in docs/art/pp001-intro.pod

Many thanks! Applied as r19702.

[perl #43613] remove 'compile' opcode

On Sat Jul 07 08:14:04 2007, coke wrote: > > This op has been long deprecated. it should be removed. I removed the opcode, regenerated the ops.num file, removed the two obsolete japh tests using the 'compile' opcode, but unfortunately another japh test fails, namely the one in examples/japh/jap

[perl #43623] [PATCH] typo in docs/optable.pod

Many thanks! Applied as r19683.

[perl #38844] [TODO] Make lint, splint and tags targets

Andy, > Then create a new lint target to support Sun Studio. You've done this recently, haven't you? > And update the tags target. What does ctags point to on your system(s)? On mine it's the emacs version of ctags, whereas the tags target in the makefile is for exuberant-ctags, which on my

[perl #40392] [CAGE] convert C to C

On Tue Jun 26 13:35:51 2007, ptc wrote: > On Tue Jun 26 06:36:50 2007, particle wrote: > > On 6/26/07, Paul Cochrane via RT at > parrotcode.org> wrote: > > > On Thu Sep 21 14:38:40 2006, particle wrote: > > > > parrot's source is littered with

[perl #38844] [TODO] Make lint, splint and tags targets

I've a question about the tags target: it searches c, perl and pmc files. Shouldn't it also search/process the .ops files (as c-language files)? Paul

[perl #40392] [CAGE] convert C to C

On Thu Sep 21 14:38:40 2006, particle wrote: > parrot's source is littered with internal_exception() calls, the bulk > (all?) of which should be converted to real_exception() calls. > internal exceptions are uncatchable, and might as well be called > C. that's bad, ya dig? > > there are plenty of

[perl #41895] [TODO] Use Getopt for argument parsing in perlcritic.t

Implemented as of r19319.

[perl #42427] [CAGE] cleanup perlcritic errors

To be able to attack this ticket properly, we need to be able to run at least a subset of the perlcritic tests with 'make test' alongside the other coding standards tests, so as to ensure that any broken windows do not remain so for very long. Therefore, I propose to change the functionality o

[perl #43241] [PATCH] [CAGE] include/parrot/string.h typedefs STRING and String are redundant

On Mon Jun 18 15:03:31 2007, petdance wrote: > > On Jun 18, 2007, at 11:28 AM, Mark Glines (via RT) wrote: > > > Here's a patch to consolidate that, and standardize on STRING (based > > on the fact that it's used *much* more often than String is). > > And also isn't String a standard C++ class?

[perl #38844] [TODO] Make lint, splint and tags targets

On Fri Apr 13 06:15:19 2007, infinoid wrote: > On Mon Apr 03 20:43:53 2006, petdance wrote: > > The lint target needs to be renamed to splint. > > > > Then create a new lint target to support Sun Studio. > > > > And update the tags target. > > As of today's date (2007-04-13), it appears that all

[perl #41569] [BUG] t/distro/file_metadata.t fails on win32

After much help from Ron Blaschke to get this working nicely on Win32, I've applied the latest patch as r19059 and am now closing the ticket. Paul

[perl #43148] [TODO] Rename rpath hash element to be more general (config/init/hints/darwin.pm)

On Thu Jun 07 05:21:33 2007, jkeen at verizon.net wrote: > Paul Cochrane wrote: > >> 'rpath' sounds pretty general to me (if not particularly > >> self-documenting). Is there really a significant bang for the buck to > >> changing it? (Or, different way of asking same question: If that > >> co

[perl #37923] [TODO] build - configure framework needs tests

On Mon Feb 20 14:35:58 2006, jhoblitt wrote: > > [jhoblitt at hawaii.edu - Wed Dec 14 01:56:56 2005]: > > > > - The framework itself needs tests!!! > > > > Parrot::Configure::Data should be low hanging fruit > > This has been mustly done since Decemeber with the expection of > Parrot::Configure

[perl #39426] [BUG] Can't build with cygwin.

cygwin is currently building (as of r18821). Is this ticket required anymore? Paul

[perl #38217] r11124: Cygwin build fails

cygwin is building as of r18821. Is this ticket required anymore? Paul

[perl #42918] [PATCH] src/library.c use mem_sys_free instead of free()

On Mon May 14 05:08:56 2007, codermattie wrote: > On Thu, 10 May 2007 12:18:00 -0700 > "chromatic via RT" at parrotcode.org> wrote: > > > On Thursday 10 May 2007 02:37:15 Mike Mattie wrote: > > > > > quick patch to use the mem_sys_free wrapper instead of using the > > > platform's free() direct

[perl #42908] [PATCH] add guard macro to autogenerated file include/parrot/has_header.h

On Tue May 08 18:44:52 2007, infinoid wrote: > Just talking to myself here :) > > On Tue May 08 13:28:41 2007, mark at glines.org wrote: > > Hmm. It seems there's more than one header being missed by > > t/codingstd/c_header_guards.t. I'm going to try to supplement the > > $DIST->c_header_files

[perl #42898] [PATCH] src/library.c , honor PARROT_PREFER_SOURCE in extension guessing

On Mon May 07 04:28:22 2007, codermattie wrote: > hello, > > Building on commit #18446 this patch honors PARROT_PREFER_SOURCE. > > quick background: > > to get the install/working-copy to work the same extensions should > not be used with .load_bytecode. Sometimes it will be compiled, > sometime

[perl #42903] [PATCH] Add guards to the rest of the headerfiles

On Mon May 07 12:55:56 2007, mark at glines.org wrote: > Hi, > > The attached patch adds a bullet to PDD07 about headerfile guards, and > adds a test to c/codingstd/ to check for existence, uniqueness, and > lack of conflicting names. Then it fixes up all headers returned by > Parrot::Distributi

[perl #41908] [PATCH] 5 feature enhancement of src/library.c (extension guessing), and solutions for the install target problems

On Mon Apr 30 12:22:21 2007, mdiep wrote: > On Wed Mar 21 03:44:10 2007, codermattie wrote: > > Hello, > > > > now that 0.4.10 has released I would like to merge rt# 41908 which > > introduces extension guessing. > > The current implementation does not affect the behavior of existing > > code. No n

[perl #42900] [PATCH] src/packfile.c Parrot_load_bytecode, improve error message

On Mon May 07 06:49:42 2007, codermattie wrote: > Hello, > > I noticed while debugging my patches to the loader that the message >for a failure in .load_bytecode was really > horrible. It was something like this: > > immc: Couldn't find file %s > > At the time I didn't know what immc was, an

[perl #42899] [PATCH] t/codingstd/tabs.t improve diagnostic output

On Mon May 07 04:40:24 2007, codermattie wrote: > Hello, > > My version of Emacs appears to be leaking tabs into files despite > having this in my emacs config: > > (setq indent-tabs-mode nil) > > To help track down the problem in emacs/cperl and get it fixed I need > better diagnostics. I have

[perl #41908] [PATCH] 5 feature enhancement of src/library.c (extension guessing), and solutions for the install target problems

Matt, This patch actually broke stuff and was reverted shortly before Parrot 0.4.10. It needs to be reapplied, and then checked that it doesn't break anything (IIRC there were problems on Win32), hence why the ticket is still open. I've only just returned from 3 weeks overseas and haven't ha

[perl #41860] [CAGE] Run Parrot under Coverity Prevent

On Thu Mar 15 19:24:31 2007, ptc wrote: > Coverity already runs Prevent on the Perl 5 source. Let's get > Parrot running under it, too. L Just to keep this ticket up to date with what's happening, here is a reply to my email asking to add Parrot to Coverity which recen

[perl #40861] [CAGE] - add a Perl::Critic policy to look for FIXME|TODO|XXX

On Mon Nov 13 06:31:40 2006, ptc wrote: > The t/codingstd/fixme.t test only looks in C-language files for > FIXME|TODO|XXX comments. It would therefore be good for the > t/codingstd/perlcritic.t test to check for these comments in the Perl > source files. Added a check for the Perl::Critic::Bangs

[perl #39878] [CAGE] generated files with timezoneless times

On Wed Jul 19 09:17:26 2006, coke wrote: > # $Id: MANIFEST 13384 2006-07-19 15:42:23Z tewk $ > # > # generated by tools/dev/mk_manifest_and_skip.pl Wed Jul 19 09:38:21 > 2006 > > Any tools that insert messages like this in generated files should > include a timezone, even if it's GMT/UTC. In f

[perl #39934] [PATCH] Make disassemble useful.

On Mon Jul 24 19:10:59 2006, tewk wrote: > I've been wanting this little enhancement for quite some time. > I finally coded it up. > Suggestions welcome. > > Kevin > > The patch updates disassemble output to contain three useful pieces of > information. > > FROM > > load_bytecode_sc "TGE.pbc" >

[perl #40361] [PATCH] #40278 [CAGE] perl coding standards coda. (cont.)

On Tue Dec 19 16:30:34 2006, [EMAIL PROTECTED] wrote: > Nicholas Clark wrote: > > > > To seek clarification - having those as global settings for cperl isn't > > likely to be an issue? Or having them in editor blocks? > > I meant globally. > > It's really not a big deal, though. For the immedia

[perl #42045] [PATCH] add return statement to clone in iterator.pmc

On Tue Mar 27 12:08:14 2007, [EMAIL PROTECTED] wrote: > On Saturday 24 March 2007 05:36, Klaas-Jan Stol wrote: > > > attached a patch that adds a return statement to clone in iterator.pmc > > (which was obviously forgotten?) > > How interesting that it didn't fail on Linux with GCC. Anyway, ap

[perl #42236] [PATCH] Codingstd/whitespace fixes (keyword one-space open-paren)

On Fri Mar 30 23:36:45 2007, [EMAIL PROTECTED] wrote: > Hi, > > I'm bored, so I'm going through and fixing some failing tests in > t/codingstd/ > > At the moment I'm working on c_parens.t. Here's one that fixes the > majority of the failures in the first third of the tests, which looks > that cod

[perl #42225] [BUG] t/codingstd/c_parens.t getting false negatives

On Fri Mar 30 21:31:53 2007, [EMAIL PROTECTED] wrote: > On Fri Mar 30 21:03:36 2007, [EMAIL PROTECTED] wrote: > > While I haven't fixed it, I've mitigated it a fair amount. The original > > version has 273 failing files. My painfully simple fix drops that to 130. > > > > My fix is just instead o

[perl #42074] [PATCH] add RECURSION_LIMIT macro

Thanks! Applied in r17863.

[perl #42156] [PATCH] Make invoke() return opcode_t*

Thanks! Applied in r17859. Note: I had to update include/parrot/debug.h to make sure that src/ debug.c

[perl #41927] [PATCH] getting gen_manifest_skip() to return correct results quickly

Actually bothering to attach the patch this time... parrot_distro.patch Description: Binary data

[perl #41168] graceful "no compiler" error message?

On Tue Mar 20 12:13:15 2007, coke wrote: > per chromatic, this should probably be backed out. At least for the > 0.4.10 release. Backed out until we find another solution to the problem. Paul

[perl #41906] [PATCH] 3 & 4 src/library.c refactoring combined and rebased against 17628 (with attatchment this time)

particle++ confirms that this works on Win32. Ticket resolved.

[perl #41168] graceful "no compiler" error message?

particle++ confirmed that this patch works successfully on windows. Closing the ticket.

[perl #41886] [CAGE] Use lcov to show code coverage

On Sat Mar 17 14:19:51 2007, ptc wrote: > The lcov tool from the Linux Test Project > (http://ltp.sourceforge.net/coverage/lcov.readme.php) can be used to > produce html output of code coverage information (I believe this looks > similar to Devel::Cover's output). A 'make cover' target should be >

[perl #39823] [CAGE] tools/dev/run_indent.pl -- this should be a test

On Mon Jul 24 19:51:24 2006, guest wrote: > > Hi Jerry, > > I've made an initial version of C. > > Can you please tell me if this is ok and what improvements are needed? > > There are a few stuff from C that I have not copied over, > I needed advice whether they are still needed? > > Thanks!

[perl #38969] [CAGE] parrot source does not conform to standards

On Mon Apr 24 12:57:16 2006, [EMAIL PROTECTED] wrote: > running `per tools/dev/check_source_standards.pl` is disheartening, as > there are thousands upon thousands of source standards exceptions. > > this is likely a combination of three things: > 1) the standards (docs/pdds/clip/pdd07_codingstd.p

[perl #41610] [TODO] Work out why regexp in is_perl_exemption doesn't search subdirs

Fixed by chromatic in r17426.

[perl #41908] [PATCH] 5 feature enhancement of src/library.c (extension guessing), and solutions for the install target problems

On Mon Mar 19 03:39:21 2007, codermattie wrote: > Hello, > > This patch begins the feature enhancement phase of the > Parrot_locate_runtime_str. > > based on: rev 17631 > > two new static functions are introduced. > > * try_load_path: > > this helper combines the path_finalization with the sta

[perl #41902] [PATCH] 3 refactor src/library.c to reduce complexity, introducing a few new static scoped path utility functions

Ticket is superseded by #41905

[perl #41903] [PATCH] 4 refactor src/library.c

Ticket is superseded by #41905

[perl #41906] [PATCH] 3 & 4 src/library.c refactoring combined and rebased against 17628 (with attatchment this time)

On Mon Mar 19 01:07:54 2007, codermattie wrote: > here is the re-based patch. please see the tickets for the third and > fourth for comments on the changes. > > this patch was compile tested. (added message to incorrect ticket, this was the right one) Applied in r17630. Thanks! I'll close this t

[perl #41902] [PATCH] 3 refactor src/library.c to reduce complexity, introducing a few new static scoped path utility functions

On Sun Mar 18 23:49:11 2007, codermattie wrote: > this is the third patch in the series of src/library.c re-factors. > > This patch is compile and test-suite tested on linux-i686. it does > include a minor change > on win32 that I was not able to test. > > I have created a few new path utility fu

[perl #41900] [PATCH] 2 refactor src/library.c to reduce complexity, eliminate duplicated code

Applied in r17628. Thanks!

[perl #41601] [BUG] parrotbug b0rken

The main problem people seem to be having with parrotbug is in sending messages. Since one needs to be online to send messages (if and when it works) why not let people just use [EMAIL PROTECTED] Then we can reserve the parrotbug program for generating bug reports offline for later reporting

[perl #41529] [BUG]: t/perl/Parrot_Distribution.t test failure

On Tue Feb 20 15:31:02 2007, [EMAIL PROTECTED] wrote: > On Saturday 17 February 2007 08:27, jerry gay wrote: > > > as noted in my svn log at time of checkin, this is a failing test > > which exposes a bug in Parrot::Distribution. '*.t' files are only perl > > files if the shebang says they are, b

[perl #41658] [TODO] Move all gc source files into a separate directory

On Thu Mar 15 19:47:07 2007, [EMAIL PROTECTED] wrote: > I have a patch for doing this, at least a build, compile, and test type > patch. Instead of doing one massive patch to send, here's a script to > move the files(diffs include the entire file twice) and apply the > patch. It moves all th

[perl #41601] [BUG] parrotbug b0rken

On Fri Feb 23 13:32:02 2007, kjs wrote: > parrotbug seems to be broken on win32. What output are you getting (if at all)?

[perl #38764] Test results of parrot on Freebsd

I've now got access to a FreeBSD (6.1 PRERELEASE #4) box, and have checked out and compiled Parrot. Attached is the output of 'make test', and myconfig. Regards, Paul myconfig Description: Binary data make_test.out Description: Binary data

[perl #41168] graceful "no compiler" error message?

On Sun Mar 18 04:05:41 2007, ptc wrote: > On Sat Mar 17 23:51:04 2007, [EMAIL PROTECTED] wrote: > > On Wed Jan 03 07:51:56 2007, coke wrote: > > > > > It would be nice if configure.pl gracefully handled the error > > condition > of "no compiler found". > > > > Here's a patch for that! > > Patch

  1   2   >