Garrett Goebel wrote:
>
> 1) Inline is case-sensative with filenames whereas Win32 is not.
>
> If you compile a simple inline c package "Foo" and rename it "FOO", inline
> will fail with "Had problems bootstrapping Inline module FOO"... errors
Is this causing problems? Why are you renaming things and expecting it
to work? I would consider this low priority, if even an Inline problem
at all.
>
> 2) There seems to be a maximum length limitation on package names
>
> OK: package abcdefghijklmnopqrstuvwxyz;
> NOT OK: package abcdefghijklmnopqrstuvwxyza;
> OK: package Win32::Struct::Abcdefghijklmnopq;
> NOT OK: package Win32::Struct::Abcdefghijklmnopqr;
>
> This may have something to do with the maximum size of a shell command using
> command.com. Which under WinNT4.0 is 127 characters. Cmd.exe on the other
> hand does not appear to have an easily reachable limit. Anyone know what it
> is?
I expect most of these length problems to disappear when I implement the
new object naming scheme. Stay tuned...
, Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
