<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 11, 2013 at 10:28 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com" target="_blank">siguctua@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im"><br>
</div>are all unix-based systems using .so extension for dynamic libs?<br>
i guess these modules left without extension on purpose to not<br>
pollute VM code with<br>
dealing with unix dialect-specificness.</blockquote></div><br></div><div class="gmail_extra">all the ones I've heard of do. Wikipedia says " In Unix-like operating systems using ELF, dynamically-loaded shared libraries can be identified by the filename suffix <tt>.so</tt> (shared object)." Solaris also uses this extension <a href="http://docs.oracle.com/cd/E26505_01/html/816-5165/ld.so.1-1.html">http://docs.oracle.com/cd/E26505_01/html/816-5165/ld.so.1-1.html</a>. There is also this page which says that "In most modern Unix-like systems [...] the filenames always start with <code>lib</code>, and end with <code>.a</code> (<a href="http://en.wikipedia.org/wiki/Ar_%28file_format%29" title="Ar (file format)" class="">archive</a>, static library) or <code>.so</code> (shared object, dynamically linked library)". <a href="http://en.wikipedia.org/wiki/Library_%28computing%29#File_naming">http://en.wikipedia.org/wiki/Library_%28computing%29#File_naming</a><br>
</div><div class="gmail_extra"><br clear="all"><br>-- <br>Damien Cassou<br><a href="http://damiencassou.seasidehosting.st" target="_blank">http://damiencassou.seasidehosting.st</a><br><br>"Success is the ability to go from one failure to another without losing enthusiasm." <br>
Winston Churchill
</div></div>