Ambiguous overload of ConfigFile::load

Minor issues with the Ogre API that can be trivial to fix
Post Reply
User avatar
Mikachu
Gnoll
Posts: 603
Joined: Thu Jul 28, 2005 4:11 pm
Location: Nice, France

Ambiguous overload of ConfigFile::load

Post by Mikachu » Thu Apr 18, 2013 8:57 pm

Hi,

ConfigFile::load() has 3 overloads :

Code: Select all

 /// load from a filename (not using resource group locations)
        void load(const String& filename, const String& separators = "\t:=", bool trimWhitespace = true);
        /// load from a filename (using resource group locations)
        void load(const String& filename, const String& resourceGroup, const String& separators = "\t:=", bool trimWhitespace = true);
        /// load from a data stream
        void load(const DataStreamPtr& stream, const String& separators = "\t:=", bool trimWhitespace = true);
... but the first 2 are actually ambiguous if you call them with 2 Strings as arguments, as the beginning of the signature is the same.
0 x
OgreProcedural - Procedural Geometry for Ogre3D

User avatar
spacegaier
OGRE Team Member
OGRE Team Member
Posts: 4293
Joined: Mon Feb 04, 2008 2:02 pm
Location: Germany
x 2
Contact:

Re: Ambiguous overload of ConfigFile::load

Post by spacegaier » Thu Apr 18, 2013 9:09 pm

Probably makes sense to create a JIRA ticket for that one.
0 x
Ogre Admin [Admin, Dev, PR, Finance, Wiki, etc.] | BasicOgreFramework | AdvancedOgreFramework
Don't know what to do in your spare time? Help the Ogre wiki grow! Or squash a bug...

User avatar
Mikachu
Gnoll
Posts: 603
Joined: Thu Jul 28, 2005 4:11 pm
Location: Nice, France

Re: Ambiguous overload of ConfigFile::load

Post by Mikachu » Thu Apr 18, 2013 9:14 pm

Done :)
0 x
OgreProcedural - Procedural Geometry for Ogre3D

Post Reply