Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » [BUG?] MIValue (Why "String &MIValue::Get(void)" is called ? it should not.)
Re: [BUG?] MIValue [message #44562 is a reply to message #44542] Tue, 31 March 2015 12:52 Go to previous messageGo to previous message
omari is currently offline  omari
Messages: 276
Registered: March 2010
Experienced Member
bug catched:

replacing rval_ by const rval_ in

		MIValue(MIValue  rval_ v);
		MIValue &operator=(MIValue  rval_ v);


=>

		MIValue(MIValue const rval_ v);
		MIValue &operator=(MIValue  const rval_ v);




rsolve the probleme with COMPILER_MSC, but create one with others compilers

the origin of the probleme is in Core/Defs.h:


#ifdef COMPILER_MSC
#define pick_
#define rval_ &
#else
#define pick_ const
#define rval_ const &
#endif



Why this difference between COMPILER_MSC and others ?


regards
omari.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: patch Gdb_MI parser
Next Topic: GDB/MINGW interface Bug fix
Goto Forum:
  


Current Time: Wed Jun 18 15:59:02 CEST 2025

Total time taken to generate the page: 0.07552 seconds