[GiNaC-devel] tinfo

[Chris Dams]

Dear Jens,

On Thu, 10 Nov 2005, Jens Vollinga wrote:

> But maybe I am mistaken. So I'd like to ask somebody who knows C++ 
> better than me, if there might be some hidden pitfalls.

Sounds like something that could work. You could try it. But please run 
"make check" before you put it in CVS ;-).
 
> Is the conversion a problem (what about 64bit machines)?

One should of course use the right type and on AMD 64 that would not be
unsigned int because it is 32 bits, while pointers are 64 bits. Is there
anything wrong with the SOMECLASS::tinfo being of type char*? That way you
would need only one variable that you could typedef to something more
descriptive (e.g. tinfo_t).

Best,
Chris