But you have to remember that gets removed to the default setting when changing the compiler selection when trying umpteen ways to fix it. Thu, 08 October Hi Paul, I tried to mock-up your problem, but it all builds and runs fine in my case.
I paste the code so that you can tell me what to add where in order to reproduce your error. Hi Mateuz, Thanks for your assistance.
The compiler does not detect cSchedulerBase is inherited and I'm calling the base constructor directly. Its time for a beer. I'll test your version in my linux eclipse tomorrow. I'll try again tomorrow.
There iss someone out there. David Vavra Messages: Registered: October I don't think it's Eclipse that's getting the error. I also tried to compile Mateusz's example and it compiled without errors. There are subtle differences between MS and gcc but I don't think they apply here. More likely the definition of cSchedulerBase is missing by perhaps some missing punctuation as I said before or there is something that results in gcc looking for a different signature than the one defined by cSchedulerBase.
Maybe the parameters you are trying to pass aren't really the same type? It seems your problem is that cSchedulerBase is not being defined as a class for whatever reason. Fri, 09 October Thanks David and Mateusz for your assistance but eclipse is doing my head in: "Clean Project" cleans up the Console perspective but not the Problems perspective.
Its best to shut down eclipse and reopen it. That includes all of its member functions and all template functions called from those. Consequently, template writers tend to place template definition in header files.
That is not actually required by the standard, but until improved implementations are widely available, we recommend that you do so for your own templates: place the definition of any template that is to be used in more than one translation unit in a header file. Unless we have a compiler that has implemented the new export keyword, placing the template member functions in a separate implementation file won't work.
Because the templates are not functions, they can't be compiled separately. Templates should be used in conjunction with requests for particular instantiations of templates. So, the simplest way to make this work is to place all the template information in a header file and to include the header file in the file that the template will be used.
Javadoc Generation 1. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:.
Email required Address never made public. Name required. Follow Following. Diaries of a Coding Mom. Powered by: FUDforum 3. Breadcrumbs Home Projects Forums. Eclipse Community Forums Forum Search:. Search Help Register Login Home. Powered by FUDForum. Page generated in 0. Sign up to our Newsletter A fresh new issue delivered monthly. Eclipse Community Forums. Forum Search:.
0コメント