Frankly, I don’t know :) Like I said I'm only learning... You know thinking it's only actually a scripting language it can be pretty powerfull, but it stays a scripting language after all. Know higher class decalrations and no higher hierarchy apart from moduls. So I'm only guessing that in large it would be quit unmanagalbe. Thinking of the enviroment we had... Brrr.. I mean we had over 3000 files ( not counting the non perl ones ) and not one of them was over 2000 in line number... That is quite not good :)
-----Original Message----- From: Andy Armstrong [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2008 2:58 PM To: Gergely Brautigam Cc: perl-qa@perl.org Subject: Re: My Perl QA Hackathon Wishlist On 25 Mar 2008, at 13:53, Gergely Brautigam wrote: > Well... We used Java with JUnit and .NET with NUnit... C++ for low > level > testing and so fort and so on.. They all had there advantages and > disatvantages. I use perl for nearly one and a half year now. But > appart > form the weird syntax and the golfs, and the perl haiqus it's a pretty > interesting language :). > > I would use JUnit and NUnit for larger project, I don't know if perl > could handle it... Heh. Perl is used for big things too you know :) What do you suspect that Perl would be unable to handle? -- Andy Armstrong, Hexten
