On Thu, Sep 28, 2006 at 09:36:13AM +0100, Nicholas Clark wrote:
>
> However, step 2 is easier for Perl because we're not trying to do portable
> bytecode. Some constants, (such as *most* of the socket constants, but I think
> not all) are defined in RFCs, so can be baked into bytecode at compile t
On Fri, Sep 08, 2006 at 12:38:39PM +0200, Leopold Toetsch wrote:
> Hi,
>
> typical socket ocde currently looks a bit unfriendly due to magic constants,
> e.g.
>
> socket sock, 2, 1, 6 # PF_INET, SOCK_STREAM, tcp
>
> I'd like to have symbolic constants for all that stuff:
>
> socke
chromatic wrote:
On Friday 08 September 2006 03:38, Leopold Toetsch wrote:
typical socket ocde currently looks a bit unfriendly due to magic
constants, e.g.
socket sock, 2, 1, 6# PF_INET, SOCK_STREAM, tcp
I'd like to have symbolic constants for all that stuff:
socket sock .
On Friday 08 September 2006 03:38, Leopold Toetsch wrote:
> typical socket ocde currently looks a bit unfriendly due to magic
> constants, e.g.
>
> socket sock, 2, 1, 6 # PF_INET, SOCK_STREAM, tcp
>
> I'd like to have symbolic constants for all that stuff:
>
> socket sock .PF_INET, .SO
