Marcel Grunauer wrote:
>
> Hi Brian,
>
Hello my friend. Long time no see. How is Vienna this time of year?
Vancouver is seemingly lovely, but of course I never get out long enough
to play. :(
> Inline-0.34 couldn't make test on perl 5.6.0 on Mac OS X, because for
> some
> reason mkdir() refuses to work if the pathname ends with a slash. Hence:
This brings up a good point. Listen up Neil, Patrick and Ryan.
I want to ensure that all paths used internally in Inline will have no
trailing '/'.
I used to go the opposite way, figuring that an operation ending in:
/my/nice/little/path//filename
was no big deal because the OS would ignore/collapse the double slash. I
think this is not true on some of the more arcane systems that 0.40 will
allow as to port Inline to. VMS for example.
I will also ensure that any '\' is normalized to '/'.
This has the following advantages:
1) $fullpathname = "$o->{inline_dir}/file.foo" will result in not having
a double slash.
2) Inline will work on Mac OS X. :)
3) The ports to VMS et al, will be easier
4) Error messages will not have pathnames with double slashes.
All this means to the I4P (Inline 0.40 Porters ;) is that lines like:
$fullpathname = "$o->{inline_dir}file.foo"
will need to be fixed to look like the previous one.
OK?
>
> I didn't try to install Inline::Tcl or Inline::Python.
Horrid buggers :)
>
> I'm really looking forward to using the Inline modules on OSX now...
> In particular, it'd be good to use the Java 2D graphics classes from
> within Perl. I'll report back on success (or failure) when there are
> some results.
Very good. This reminds me. At some point I'd like to set up a website
of Inline testimonials. If anyone wants to send me a ~300 word abstract
of how they've used Inline, I could get that going. I'll try to get a
redirect from http://inline.perl.org
Bye Marcel...
Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
