[IGSTK-Developers] Borland compiler and StateMachine macro

[Julien Jomier]

Hi Luis,

bcc doesn't like the extra line either...

I propose to add the following lines at the end of the macro:

#ifdef __BORLAND__
   // This variable is added to support broken bcc compiler
   char mydummychartypeforbcc
#endif

What do you think?

Julien

Luis Ibanez wrote:
> 
> Hi Julien,
> 
> Thanks for looking into the Borland errors.
> 
> This is interesting, specially since an empty
> statement (e.g. an isolated ";" is supposed to
> be acceptable anywhere...
> 
> I wonder if Borland will be happier with:
> 
>   private:
>      ;
> 
> 
> meaning that we add a couple of empty lines
> to the declaration of the Macro.
> 
> or... another option if to put an #ifdef BORLAND
> in the macro...
> 
> If you have a chance, could you please give it
> a try to the extra blank line and let us know
> what you find ?
> 
> 
>    Thanks
> 
> 
>      Luis
> 
> 
> --------------------
> Julien Jomier wrote:
> 
>> Hi all,
>>
>> I was looking at the compiling error on bcc32 and found out that 
>> Borland compiler doesn't like:
>>
>>   private: ;
>>
>> The problem comes from the macro
>>
>> igstkStateMachineMacro();
>>
>> This macro ends by: 'private:' so the semicolon at the end causes bcc 
>> to report an error.
>>
>> We have two options (AFAIK):
>>
>> 1) write:
>>   igstkStateMachineMacro()
>>
>> instead of
>>
>>   igstkStateMachineMacro();
>>
>> 2) Add something like: 'char dummy' at the end of the macro...
>>
>> I prefer the second option and maybe there is another alternative,
>> let me know what you think,
>>
>> thanks,
>>
>> Julien
>>
>> _______________________________________________
>> IGSTK-Developers mailing list
>> IGSTK-Developers at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>>
>>
> 
> 
> 
> 
> 
>