Garrett Goebel wrote:
> 1) Inline::Struct
> I've been looking at your OO Inline example. ...And thinking that it would
> be nice if there were an Inline::Struct to provide an OO interface to define
> structures similarily to the interface Class::Struct uses. -But something
> which would facilitate their use in Inlined languages.
This type of thing comes up a lot in discussions. I'm not a big fan of
coming up with some automatic C<->Perl interface format. I like to do
things that are almost always right. Slam-dunks, no-brainers. I think
that stuff can be a can of worms. But we need worm-handlers in the
world, so don't let me discourage you. I would never let you discourage
me :)
>
> I'll probably bang my head against that wall for a little while, and see if
> I can't make something that shows enough promise to merit further attention.
>
> 2) More detailed documentation for the bone-headed on best practices when
> manipulating [AHIS]V's. Yes much of the general stuff is in perlguts,
> perlapi, perlxs, etc. But a coherent discussion of practical implementation
> details would be most excellent. Checking for read-only values, objects and
> references, magic, do's and don't's, etc.
Now your talkin'. This is a slam-dunk. We need better doc for sure. If
you want to take the doc helm for a while, then I say "Aye-aye".
The best way to do this is through patches.
1) Get a copy of makepatch from CPAN
2) Get the latest Inline source.
3) Untar the source.
4) Make a complete copy of the whole directory.
5) Modify the copy anyway you wish.
6) Say 'makepatch Inline-0.31/ Inline-0.31.modified/ >
Inline-0.31-patch'
7) Send me the patch.
> 3) Some of your earlier comments on Inline included creating an abstraction
> layer between XS and the end user (not the perlapi mind you). I'm curious,
> whether or not this is still intended, and how you plan to go about it. I
> believe (unless the cloud of my ignorance is too thick) that typemap support
> currently drops you off into the wilds of XS.
I always believe in doing the right thing, where 'right' means helping
the most people. Typemapping is ugly, but not terribly so. And there's
really not a cleaner way to do it. Plus, some people have been
typemapping for years. Why throw away those typemaps when you can just
drop them into Inline unmodified? You don't ever *have* to use typemaps.
You can always map your types inline. But they're a really nice feature.
I actually consider Inline's use of typemap to be its biggest
innovation.
FYI, Inline happens to be a very gentle intro to XS. It's OK to
understand XS. I just want Inline to be so rockin' that you'd have to be
nuts to use XS on a regular basis. We're not there yet, but we will be.
>
> Thanks. In in case I haven't mentioned it recently... Inline is wonderful as
> is. Future improvements are so much icing on the cake.
I have not yet begun to bake...
Cheers, Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
