Ken,
Did anyone ever respond to this? I don't think so. My apologies.
I doubt Neil and I will get a chance to consider it until after TPC5.
(Maybe some else out there? </HINT> :)
I look forward to talking to you at TPC5, if not YAPC/NA. I'd bet
Inline::MoC will be both doable and beneficial.
If you get a chance do start working on it yourself, please drop a line.
We'd be glad to help you along.
Cheers, Brian
Ken MacLeod wrote:
>
> Hi folks, I'm working on a preprocessed-C-based extension language
> called Mostly-C, as part of the Orchard processing library[1]. It's
> similar to SWIG except that it's intended for writing *new* C code
> instead of wrapping existing C code. Mostly-C uses a transparent
> bridge (or binding) between Perl and Mostly-C, so there's no XS coding
> involved, just MoC's own wierd syntax.
>
> Mostly-C uses garbage collection, attribute syntax, and object methods
> to make writing extensions much easier. Porting Matt Sergeant's
> XML::XPath::Step module[2] into Mostly-C is an excellent example of
> what the code looks like. There's also a quick summary to the
> preprocessor syntax[3]. I'm hoping there can be a better preprocessor
> someday when we can implement a real parser (rather than just
> regexps).
>
> I'm writing this intro now because my schedule doesn't have an
> Inline::Mostly-C in it for likely a couple of months because of my
> existing schedule, I'm just starting into a new job, and moving out of
> state. I'm hoping someone can pick up Inline::Mostly-C and run with
> it. I will be able to support anyone who wants to work on it.
>
> Email me if you'd be interested. Thanks,
>
> -- Ken
>
> [1] <http://casbah.org/~kmacleod/orchard/>
> [2] <http://casbah.org/~kmacleod/orchard/xpath.moc.txt>
> [3] <http://beauvoir.phil.unc.edu/groves/29>
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
