Could not figure out why inserting into a boost::multi_index container is creating a compilation issue that starts off with c:\code\common\lib\boost\boost\detail\allocator_utilities.hpp(153) : error C2061: syntax error : identifier 'p' and then a lot of errors.. I am compiling in Visual Studio 2005. Has anybody seen a similar problem? Thanks, Ram

Hi Joaquin, Thanks for your help! I tried creating a project and turned "Using precompiled headers to "Not using precompiled headers" and tried your code. That compiled! I think I should do that in my project too, will try that and let you know, but I am not sure I can do that in our official code. Will try that and let you know anyway. But thanks a lot for your help! My first real multi_index program worked! Thanks, Ram

Hi, I simplified my problem to make sure it was not because of my class or something like that, this is the exact content(related to boost::multi_index) in the header file, example.h #include #include #include using namespace boost::multi_index; using boost::multi_index::multi_index_container; using boost::multi_index::hashed_unique; using boost::multi_index::indexed_by; typedef multi_index_container< int, indexed_by< hashed_unique

int_multiset;

and then below it in the header file I have my class written, as follows, class MgrABC : public MainManager { public: int_multiset sample1; <already existing code> . . . protected: virtual void _handler(); <already existing code> . . . }; In the corresponding cpp file example.cpp void MgrABC::_handler() { . . . this->sample1.insert(1); <already existing code> . . . } This simple code is not compiling with this same error, Exact build output, Compiling... example.cpp c:\sample\common\lib\boost\boost\detail\allocator_utilities.hpp(153) : error C2061: syntax error : identifier 'p' c:\sample\common\lib\boost\boost\multi_index\detail\index_base.hpp(105) : see reference to function template instantiation 'void boost::detail::allocator::construct<int>(void *,const Type &)' being compiled with [ Type=int ] c:\sample\common\lib\boost\boost\multi_index\detail\index_base.hpp(102) : while compiling class template member function 'boost::multi_index::detail::hashed_index_node *boost::multi_index::detail::index_base::insert_(const int &,boost::multi_index::detail::hashed_index_node *&,boost::multi_index::detail::lvalue_tag)' with [ Super=boost::multi_index::detail::index_node_base, Category=boost::multi_index::detail::hashed_unique_tag, Value=int, IndexSpecifierList=boost::multi_index::indexed_by>, Allocator=std::allocator<Vs32> ] c:\sample\common\lib\boost\boost\multi_index\hashed_index.hpp(93) : see reference to class template instantiation 'boost::multi_index::detail:: index_base' being compiled with [ Value=int, IndexSpecifierList=boost::multi_index::indexed_by>, Allocator=std::allocator<Vs32> ] c:\sample\common\lib\boost\boost\multi_index_container.hpp(100) : see reference to class template instantiation 'boost::multi_index::detail:: hashed_index' being compiled with [ KeyFromValue=boost::multi_index::identity<int>, Hash=boost::hash<int>, Pred=std::equal_to<int>, SuperMeta=boost::multi_index::detail::nth_layer<1,int,boost: :multi_index::indexed_by>,std::allocator<Vs32>>, TagList=boost::mpl::vector0boost::mpl::na, Category=boost::multi_index::detail::hashed_unique_tag ] c:\sample\example.h(102) : see reference to class template instantiation 'boost::multi_index::multi_index_container' being compiled with [ Value=int, IndexSpecifierList=boost::multi_index::indexed_by> ] Build log was saved at "file://c:\sample\build\bin\ sample\win\Debug\obj\BuildLog.htm" Sample - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Thanks, Ram

We dont have new #defined to anything else, just to be safe we have a customNew that we use, that will only be called if we use "customNew". A call to new will only call new, nothing different will be called.. Thanks, Ram

Hi, Hope this is a clue, if I replace "this->sample1.insert(1);" to "this->sample1.find(1);" it compiles fine. Thanks, Ram On Wed, Sep 21, 2016 at 11:51 AM, Ram wrote:

Hi Joaquin,

I hope the new complete code I gave is complete and verifiable on its own and people here can help. Struggling with this error for the last two days.

Thanks, Ram

Attached my allocator_utilities.hpp to this mail. When I tried replacing, this->sample1.insert(1); by, int x=0,y=0; boost::detail::allocator::construct(&x,y); this is the compilation output(changed the file name/directories in the previous example too), Compiling... example.cpp c:\sample\common\lib\boost\boost\detail\allocator_utilities.hpp(153) : error C2061: syntax error : identifier 'p' c:\sample\example.cpp(389) : see reference to function template instantiation 'void boost::detail::allocator::construct<int>(void *,const Type &)' being compiled with [ Type=int ] Build log was saved at "file://c:\sample\build\bin\sample\win\Debug\obj\BuildLog.htm" Sample - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Thanks, Ram

Hi Joaquin, I am not sure what I did wrong. I not been Top Quoting after you asked me to and I am trying to follow the guidelines. Not sure what I did wrong here. Thanks, Ram

[The problem is that you're not quoting at all. You should be inline quoting with minimal (but not zero) context, similar to this reply.] Will take care next time. Is this reply fine? -Ram

El 21/09/2016 a las 13:58, Ram escribió:

Hi Joaquin,

[Please do follow this list's posting guidelines and keep the formatting clear]

Will make sure I am clear about what I am speaking about(by quoting whats required).

The my compilation output after the change to [ int x=0,y=0; boost::detail::allocator::construct(&x,y);]

in allocator_utilities.hpp help?

Yes, it shows that the problem seems not to be really connected to Boost.MultiIndex. My hunch is this is related to the precompiled header effect you talked about some posts ago, or that there's an evil macro affecting this very simple code. In any case, please follow these steps so that we can narrow down the problem: 1. Continuing with your example.cpp file, where you last inserted the boost::detail::allocator::construct bit, please remove all usage of Boost.MultiIndex and its headers, and simply add this #include #include and keep the boost::detail::allocator::construct portion. Still the same " syntax error : identifier 'p'" error? 2. If the answer to the above is affirmative, please start removing headers (and the code that depends on them), *one header at a time*. Continue after you've removed everything (a) or suddenly the error disappears (b). 3. If (a), then you have a barebone example.cpp file with little more than the the allocator_utilities.hpp #include and the boost::detail::allocator::construct line. My bet is then the error has to do with the settings of your project. 4.If (b), examine the last header you removed when the error vanished. Is it introducing any kind of macro, ::new overload, or something suspicious? Please answer *inline* to this post with the feedback for each step. Joaquín M López Muñoz

[To make sense of evil macro errors, I often end up resorting to looking at the preprocessed source.] Sure thanks Dominique! But I am 100% sure there is no redefinition of new in our code here. We use another version "customNew" to use a safer "new". Joaquin, I forgot to mention that changing "Use preprocessed headers" to No/Yes did not make a difference. I confirmed this by running the stand alone test program in both modes and it was successful in both. So I was thinking of ruling that possibility out. About the steps you asked me to follow to experiment to narrow down the problem, I will do that today and reply to you. Thanks, Ram On Wed, Sep 21, 2016 at 8:36 PM, Dominique Devienne wrote:

On Wed, Sep 21, 2016 at 4:56 PM, Joaquin M López Muñoz < joaquinlopezmunoz@gmail.com> wrote:

...

El 21/09/2016 a las 13:58, Ram escribió:

Yes, it shows that the problem seems not to be really connected to Boost.MultiIndex. My hunch is this is related to the precompiled header effect you talked about some posts ago, or that there's an evil macro affecting this very simple code.

To make sense of evil macro errors, I often end up resorting to looking at the preprocessed source. Right-click your .cpp file in Visual Studio, Properties, Configuration Properties, C/C++, Preprocessor, and change Preprocess to a File to Yes (/P). Then CTRL-F7 that file, and look for the .i on your disk. The file will be big, but look for your own code in there, at the end, and related to the error you get, and if a macro replaced your program text in an unexpected manner, you'll know the evil macro's name (the original name in your code, now replaced to some crap that doesn't compile), and can try to find it in the header you #include (directly or not). Not sure if this works with precompiled headers. --DD

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

On 29/09/2016 01:23, Ram wrote:

...

2. If the answer to the above is affirmative, please start removing headers (and the code that depends on them), *one header at a time*. Continue after you've removed everything (a) or suddenly the error disappears (b).

The error disappears only when I remove the multi_index declaration. After which the thing is of no use to me.

Previously you have said that using it standalone in a separate project works correctly. This means that the problem is either with the project settings or with other things you have #included. If you have really tried removing *every other* #include (including stdafx.h and any other project-specific includes) so that it still fails when you include nothing but the Boost and CRT headers, then that suggests the problem is your project settings. (More likely, though, you forgot that stdafx.h was one of the headers you should have tried removing. So try that. You will have to disable precompiled headers when you do that.)

On 29/09/2016 16:54, Ram wrote:

Will try this after I try the other suggestion in the other thread of seeing the pre-processor output and trying to figure out if something is messed up there. I want to try this later since I am working on a huge project and this file is huge by itself and has over 15 or more includes.

You can do it the other way around as well. Create a new cpp file in your project that has nothing but the STL and Boost includes (no stdafx.h) and some basic exercising code and see if it compiles (it should, unless the problem is a project setting). Then gradually add your app-specific headers one at a time until it breaks. If it's a "big" header that breaks it (like stdafx.h itself), then try adding the individual includes within that header instead of including the header itself, again one at a time until it breaks. If there's lots of includes, you can do a bisection search on it -- add half at a time, then if it breaks remove half of those, etc. If you're careful this can be a bit faster sometimes but it's probably simpler to stick to one at a time if your compile times are fairly short (which they should be if you're just compiling the one file each time).