Re: 3 subroutines with same name

2006-11-21 Thread chromatic
On Tuesday 21 November 2006 18:36, James E Keenan wrote: > 3 identically named subroutines: 2 in modules and 1 in a script. And > all 3 will be in modules as I'm planning to refactor much of pmc2c.pl > into a module called Parrot::Pmc2c::Utils. (For drafts of these > revisions, see http://thenc

3 subroutines with same name

2006-11-21 Thread James E Keenan
Note the results: [parrot] 502 $ ack 'sub gen_c' lib/Parrot/Pmc2c.pm 1221:sub gen_c { lib/Parrot/Pmc2c/Library.pm 134:sub gen_c { tools/build/pmc2c.pl 821:sub gen_c { 3 identically named subroutines: 2 in modules and 1 in a script. And all 3 will be in modules as I'm planning to refactor m

Re: pmc2c.pl: Proposed Strategy for Revisions and Testing

2006-11-21 Thread James E Keenan
Allison Randal wrote: Go with the more extensive and thoroughly tested refactor. Particle will work with you (mentoring/code review) and make sure your changes get checked in. As my 2nd post noted, I made an error in counting the number of subroutines that could be deprecated. Only gen_