# from Sisyphus
# on Tuesday 26 September 2006 10:07 pm:
>> It sounds like your use-case is more
>> along the lines of "generate the XS and start a module around it."
>
>Yep.
>
>...
>If there was something there that you wanted my response to, just let
> me know and I'll try to oblige :-)
Mostly just brainstorming at this point. I think we agree that Inline
should provide some functionality to dump XS code. In your use-case, I
think it would be best to create an external tool to automate the
module creation (hence the Module::Starter reference.)
>If this functionality were to be achieved through a module in the
> "Module" namespace, does it still hook into the Inline::C functions
> (ie does it 'require "Inline/C.pm";' ) ? Or does it work entirely
> independent of the Inline modules ?
It would definitely require Inline to transform from inline to xs code.
But, creating MANIFEST, etc shouldn't be a task for anything in the
Inline space.
--Eric
--
We who cut mere stones must always be envisioning cathedrals.
--Quarry worker's creed
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
