<br><br><div class="gmail_quote">On Sat, Nov 7, 2009 at 3:18 AM, Nirbheek Chauhan <span dir="ltr"><<a href="mailto:nirbheek@g.o">nirbheek@g.o</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Nov 6, 2009 at 1:42 AM, Petteri Räty <<a href="mailto:betelgeuse@g.o">betelgeuse@g.o</a>> wrote:<br>
> In the past when smaller arches were not that active we used to mark<br>
> Java packages stable after testing by at least one arch team. The<br>
> probability to find arch specific issues in something like Java is not<br>
> so high so I think arrangements like this are acceptable when the arch<br>
> teams have problems keeping up.<br>
><br>
<br>
</div>I think the same should be extended to other languages such as Perl<br>
and Python (unless they have portions which are C/C++)<br>
<font color="#888888"><br>
</font></blockquote><div> </div><div>You can't really, although Perl has a vm of sorts, the per-arch differences that occur as a side effect of endianness, different floating point/integer math ( 32bit vs 64bit ) , and all those differences impact code.<br>
<br>and XS modules of course, they're prone to everything C is prone to.<br></div></div><br>-- <br>Kent <br><br>perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"<br>
<br><a href="http://kent-fredric.fox.geek.nz">http://kent-fredric.fox.geek.nz</a><br>
|
