Guy,
As a follow-up to a discussion a few days ago about binding parrot to
C++ functions, is making it possible to compile parrot with a C++
compiler a 'Bad Thing'?
If anything, it should strengthen the code base. I had a dabble a few
weeks ago to see how big a job it would be, and quickly came across a
K&R function prototype bletch in auto/alignptrs/test_c.in. Although it's
too soon to say, the main tasks would be:
* avoid C++ keywords (e.g. namespace/class)
* add explicit casting
* be more careful with typing
* add appropriate extern "C"s
If I see positive feedback, I'll suggest that we create a branch for an
ongoing project from which improvements can be cherry-picked. If it's
pointless due to showstoppers (e.g. like inline assembler not being
supported) then I'll sweep the idea under the carpet.
(And if I get mixed reaction, I'll just submit some small patches to fix
a few things that I found)
Cheers,
Nick
