yade-users team mailing list archive

[Vaclav SMILAUER <eudoxos@xxxxxxxx>]

The best way to avoid symbol-renaming confusion would be to have a 
directory with deprecated headres of this style:

OldClassName.hpp:

#warning class OldClassName has been renamed to NewClassName etc.
#include"NewClassName.hpp"
#define OldClassName NewClassName

Perhpas this is too much work... Alternatively, a single yade-compat.hpp 
could contain the #defines/typedefs.

Vaclav

PS. For the conversion of old code, I recommend perl's in-place 
substitutions, something like

  perl -pi~ -e's/\bOldClassName\b/NewClassName/g' *.cpp *.hpp

> Bruno Chareyre said:     (by the date of Tue, 21 Nov 2006 15:37:42 +0100)
> 
>> Hey Janek or Vaclav
>>
>> It looks like the names of some classes have been changed. Could you 
>> send an explanation of how to use yade-scripts efficiently so that yade 
>> users in 3S don't spend hours to change the names manually in their own 
>> classes? ;)
> 

_______________________________________________
Yade-users mailing list
Yade-users@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-users