[Rcpp-devel] Defining template specialisation for wrap on Windows 64bit (Compilation error: 'result_type' does not name a type)

Renaud Gaujoux renaud at mancala.cbio.uct.ac.za
Fri Oct 4 17:45:29 CEST 2013


I posted the follow up email adding [SOLVED] to the subject, but I thought
it would appear in the same thread. Here it is:

http://lists.r-forge.r-project.org/pipermail/rcpp-devel/2013-October/006555.html

Indeed, one of the suggested solution out there was to add "typename" in
the typdef statement, but I don't control that piece of code, which is in
Rcpp itself. Maybe Dirk and Romain can look into the implications of that
for the next release?

I eventually managed to get RcppOctave working on Windows!!! The library
issue got solved by using proper gcc linking flags, making the libraries
nicely dynamically loaded.
I want to start another thread on the Rcp and RcppOctave list, to ask
willing windows users to actually test the binary package I built on
R-3.0.2.
I see strange things happening when building/checking the package in the
crappy cmd.exe terminal on my VirtualBox Windows7 (which makes me even
happier to run Ubuntu ;) ), so I'd rather ask plain R/Windows users a hand.

Thanks again for your inputs.

Bests,
Renaud

On 4 October 2013 17:30, Steve Jaffe <sjaffe at riskspan.com> wrote:

> Sorry it didn't fix the problem. (I'd still recommend making the change
> for the reasons I gave.)****
>
> ** **
>
> I don't see your follow up email yet, so I'll take a guess and say that
> you may be missing a "typename", something like:****
>
> ** **
>
> *typedef** typename OUT result_type ;*
> **
> ******
>
> This was my first thought on seeing the error; I've seen many like it and
> that's usually the reason. ****
>
> ** **
>
> But I couldn't convince myself of why the C++ rules would require a
> typename in that spot.  ****
>
> ** **
>
> But the rules are sufficiently arcane that, in general,  it's worth
> inserting a typename or two whenever the compiler says that something
> isn't what it "obviously" is (and templates are involved.)****
>
> ** **
>
> (Support your local C++ compiler! It has a (provably) tough job to do. :-)
> ****
>
> ** **
>
> Good luck,****
>
> Steve****
>
> ** **
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20131004/972dba53/attachment.html>


More information about the Rcpp-devel mailing list