Re: ver. 4.0 std include files type conflict
- Posted by mattlewis (admin) Mar 18, 2009
- 846 views
I found what is causing the type conflict error.
If a user places a 'with trace' at the top of the
of map.e include file and the user program is using
the map.e in a program; starting the program will report
the following error.
It's giving a misleading error. It's not a 'type conflict error' that's being reported. The actual issue is that a default namespace declaration must be the first token to be parsed in a file. Comments are ok, but nothing else.
I think that what's going on is that namespace is determined to be a forward type reference, and so it defines a new variable named mapnamespace isn't a reserved word, though maybe it should be. Then it comes across a type named map, and now you have multiple symbols in the same scope with the same name.
Matt
