Mathemagix

[Grégoire Lecerf <address@concealed>]

> After the modifications generic -> string in the two files,
> everything compiles as a charm for me. I made the changes on SVN;
> please retry to be sure that we are doing the same thing.
>   
I do not like this solution because it does not prevent from future 
similar crashes.
Danger might also come from the outside the basix library if static 
variables are not handled in a
robust way. The solution I proposed in mixed_symbol.hpp is standard. As 
for the desallocation problem
caused by the "new" without explicit destruction (although the 
destruction is actually done
properly at the very end of the exit) can be simply avoided by:
TMPL_DEF
class mixed_symbol_rep REP_STRUCT {
public: // FIXME: should become private
 static table<Mixed_symbol_rep*,C,eq_op>& mixed_symbol_entries () {
   static table<Mixed_symbol_rep*,C,eq_op> t((Mixed_symbol_rep*) NULL);
   return t;
 }
Does it suit you? -- There's no speed-down :-)
More sophisticated solutions, used in boost, are based on a special 
class called "smart pointer".
Grégoire.