On Sat, 22 Jul 2006 08:59:13 -0400, John Peacock wrote: Hi John
> The problem is one of communication and insufficient testing, not > architectural. I didn't think to test on a machine that didn't have > *either* M::B or version.pm installed (which is the only case where > there is any problem). Additionally, I was busy with real life and OK. Many thanx for the clarification. I started a new job last Monday, and none of the machines have either version or M::B, so I was holding off installation, being distressed by the confusion, and not wanting to land in hot water. > What you are both unaware of is that the XS code is the reference > implementation, and is exactly the same code as appears in Perl > v5.10.0 and has been basically stable for 8 months (some minor > edge cases notwithstanding). The pure Perl implementation is newer, > but no less stable. OK. > distribution. He may reevaluate that now; I am fully prepared to > maintain a parallel code inside M::B (since the code is already > modular enough to support that). OK. So what steps do you suggest I take, exactly (in my situation only)? -- Cheers Ron Savage, [EMAIL PROTECTED] on 23/07/2006 http://savage.net.au/index.html Let the record show: Microsoft is not an Australian company
