Quoth [EMAIL PROTECTED]: > +--------+--------+--------------------------------------------------------+ > | Offset | Length | Description | > +--------+--------+--------------------------------------------------------+ > | 0 | 8 | 0xFE 0x50 0x42 0x43 0x0D 0x0A 0x1A 0x0A | > | | | Parrot "Magic String" to identify a PBC file. In C, | > | | | this is the string C<\376PBC\r\n\032\n> (ASCII) or | > | | | C<\xfe\x50\x42\x43\x0d\x0a\x1a\x0a>. | > +--------+--------+--------------------------------------------------------+
This is probably too late for a change like this, in which case ignore me, but I don't suppose there's any chance that pbc files could allow an optional #! line, so that they can be used as executables directly? Parrot would need an option analogous to gcc's -x, of course, to specify to type of a file explicitly rather than inferring it from the extension; but IMHO that also would be a good thing in itself. Ben -- You poor take courage, you rich take care: The Earth was made a common treasury for everyone to share All things in common, all people one. [EMAIL PROTECTED] 'We come in peace'---the order came to cut them down.
