On Tue, 19 Jun 2001, Christian Bauer wrote:
On Tue, Jun 19, 2001 at 12:41:04PM +0200, Richard B. Kreckel wrote:
1) failure to recognize `unsigned' as `unsigned int',
This is used in many places in GiNaC. Why has it not been a problem before?
It is a problem sometimes, then again it is not, then it is a warning... I don't know.
#include <list.h> struct foo { list<foo> children; };
This is supposed to work? Methinks that to make a list<foo>, the compiler would need to know at least sizeof(foo) which it can't because the struct definition is not closed yet.
Nonsense. It's heavily used for building up all sorts of trees where it really becomes convenient. BTW, on those compilers plagued by the abovementioned problem `struct foo { vector<foo> children; };' works like a charm but according to your reasoning it would be a problem as well. Regards -richy. -- Richard Kreckel <Richard.Kreckel@Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/>