Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Re^5: Perl 5 -> 6 do's and don'ts? (Inline::C)

by tye (Sage)
on Aug 01, 2003 at 20:52 UTC ( #280137=note: print w/replies, xml ) Need Help??

in reply to Re: Re^3: Perl 5 -> 6 do's and don'ts? (Inline::C)
in thread Perl 5 -> 6 do's and don'ts?

You seem to have misunderstood my point. I don't care how the C code is generated.

The issues involved are entirely those of the perl API

Yes, and my point was that it can be very useful to write stuff in Inline::C that makes absolutely no reference to the perl API. You simply write C code that takes C-style arguments. If you do that, then you don't need any macros or processing of the source code other than whatever needs to happen to turn the perl subroutine arguments into C data types and to turn the returned C data type into a Perl scalar.

And the available transformations to/from C data types are quite limited so you won't be doing anything in that part of your C code that won't be tons easier to implement than the whole typemap power of XS.

Yes, you certainly can write Inline::C code that will be horribly hard to port. I thought you two covered that point rather well. But I don't consider that the most important point.

                - tye
  • Comment on Re^5: Perl 5 -> 6 do's and don'ts? (Inline::C)

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://280137]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (7)
As of 2018-06-20 12:43 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (116 votes). Check out past polls.