<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Nov 23, 2010 at 9:46 PM, Gabor Szabo <span dir="ltr"><<a href="mailto:szabgab@gmail.com">szabgab@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Nov 23, 2010 at 5:33 PM, Ronen Angluster <<a href="mailto:beerholder@gmail.com">beerholder@gmail.com</a>> wrote:<br>
> i can't use Moose cause of legal & corporate issues. lets not dwell on this,<br>
> its a life fact<br>
> and we came to peace with it.<br>
<br>
</div>Does the corporate policy forbid anything from CPAN or only Moose?<br></blockquote><div>as a thumb role, we prefer not to introduce any new CPAN modules into the system.</div><div>the "cost" of such actions dictate that we should strive to build things in-home</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Would you be able to use 5.14 if it came out tomorrow with "real classes"?</blockquote><div>nope. this would take time, but if such a feature would become available it would</div><div>help us advocate this change </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> unit testing will take us a long way, but not long enough.<br>
> a major chunk of our code rely on the output of other components which at<br>
> times cannot be covered<br>
> in a unit test. so we're left with some of the code checked, while some use<br>
> cases might slip<br>
> the coder & reviewer's keen eyesight and pop like mushrooms on a dung heap<br>
> at a customer's site...<br>
> not a pleasant thought...<br>
<br>
</div>I don't think the Perl community can help overcoming corporate policy<br>
and lack of testing.</blockquote><div>yes, but right now, perl way of operation the OO environment is a major</div><div>issue that cause people to look at it as a mer scripting language.</div><div>look, you can scream "real applications can be built with perl" as loud as you want,</div>
<div>but it wont convince people unless it has the right features.</div><div>as it is, since the only way to real verify typos and method calling written in the code</div><div>is to actually run it. evaluating code that should failed in compile time </div>
<div>cost a lot in programmer hours. its a feature that perl is missing. but unfortunately</div><div>i don't think we'll ever get it.</div><div>however, i am working on a code evaluating class at my own spare time,</div>
<div> when it'll be market worthy i'll add it to CPAN's repository.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Have you proposed to management to invest in tools that will help solving<br>
some of the issues you have?</blockquote><div>more then once, and we are working on such solutions. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color="#888888"><br>
<br>
Gabor<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Perl mailing list<br>
<a href="mailto:Perl@perl.org.il">Perl@perl.org.il</a><br>
<a href="http://mail.perl.org.il/mailman/listinfo/perl" target="_blank">http://mail.perl.org.il/mailman/listinfo/perl</a><br>
</div></div></blockquote></div><br></div>