Hans, so your proposal is to split the current pdpcap in 2 different objects: one for live (net device) capturing and a second one for pcap file reading? <div><br></div><div>I like Mathieu's suggested name:1) the Mathieu's reasoning about naming, 2)the objects I think is differentiated of pdp, 3)doesn't lost enterely his original name pd-pcap,<br>
<br><div class="gmail_quote">On 1 October 2010 14:20, Mathieu Bouchard <span dir="ltr"><<a href="mailto:matju@artengine.ca">matju@artengine.ca</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 Thu, 30 Sep 2010, Jordi Sala wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes it can be renamed, I named pdpcap when I started the object (PD+PCAPlib)...,... pcap could be a good name....any suggestions?<br>
</blockquote>
<br></div>
name the package "pd-pcap" and the pd library file "pcap.pd_linux" for example.<br>
<br>
Several programming languages use such naming... the hyphen makes it like a namespace in the package-manager, and the complete lack of the "pd-" prefix in the context of pd makes it look like you're loading the original "pcap" itself into Pd (which, of course, makes a lot more sense if that's exactly what your lib does : a plain wrapper and nothing else). I think that this is the kind of naming that users of several other programming languages have come to expect (Perl, Python, Tcl, Ruby, PHP, etc.)<div>
<div></div><div class="h5"><br>
<br>
_______________________________________________________________________<br>
| Mathieu Bouchard ------------------------------ Villeray, Montréal, QC</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jordi Sala<br><a href="http://musa.poperbu.net">http://musa.poperbu.net</a><br>
</div>