Skip Menu |

This queue is for tickets about the autovivification CPAN distribution.

Report information
The Basics
Id: 71878
Status: rejected
Priority: 0/
Queue: autovivification

People
Owner: Nobody in particular
Requestors: 'spro^^*%*^6ut# [...] &$%*c
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Concerning C++ compatibility
See commit <http://perl5.git.perl.org/perl.git/commitdiff/f39efbfaef55>. It corrects code that I copied from your autovivification module. I just thought this might be of some help.
Show quoted text
> See commit <http://perl5.git.perl.org/perl.git/commitdiff/f39efbfaef55>. > > It corrects code that I copied from your autovivification module. > > I just thought this might be of some help.
In the absence of any official policy regarding perl C++ compatibility, I decided not to support C++ in any of my modules. It is stated explicitely in the documentation that $Config{cc} is a C compiler, so I trust perl for putting a C compiler in $Config{cc}. The only exception I make is for Variable::Magic, because it is depended upon by other key modules that want to be smoked regularly against perls compiled with C++. Thus, the copy of ptable.h that is in Variable::Magic can be compiled by a C++ compiler (and is somewhat better than this fix in the core, because it doesn't force the casts when it is compiled by a C compiler). I may update the copy of ptable.h in a future release of autovivification, but that doesn't mean autovivification will build with a C++ compiler since I wrote all the XS in C. Vincent.