anonfagola/gmapi

Automatically exported from code.google.com/p/gmapi

gmapi's Issues

Boolean initialization now causes segmentation fault due to new definition in 0.6.1.

*What steps will reproduce the problem?*
1. Use gm::CGMVariable(true) or gm::CGMVariable(false);

*What is the expected output? What do you see instead?*
In order to maintain backwards compatibility (and in general, usability, 
after all, there's quite a few times when functions will return boolean 
values), it should initialize CGMVariable with a boolean value rather than 
setting the string disposal setting.

*Please provide any additional information below.*
Suggested patch:
* Change argument number for string disposal setting and add following 
function definition to CGMVariable:
{{{
      /// Ctor( bool aValue )
      ///   Initializes the variable to specified bool value
      ///   (it will be casted to double) and sets its type
      ///   to "real".
      ///
      /// Parameters:
      ///   aValue: Initializing value.
      ///
      CGMVariable( bool aValue ): m_isString( false ),
                                     m_stringDispose( true ),
                                     m_stringPtr( NULL ),
                                     m_real( aValue ) {}
}}}

Original issue reported on code.google.com by [email protected] on 17 Feb 2010 at 6:24

Initalizing an empty string causes an invalid CGMVariable.

What steps will reproduce the problem?
==================
1. gm::CGMVariable s(""); OR
2. gm::CGMVariable s(std::string(""));

What is the expected output? What do you see instead?
==================
A CGMVariable with a valid, empty string.

Original issue reported on code.google.com by [email protected] on 17 Feb 2010 at 6:30