T O P I C R E V I E W |
WalderMort |
Posted - Aug 11 2007 : 11:59:42 AM Nothing serious, but it would be nice to see this corrected in the next version.
In C++ I declare a struct and then later derive a new struct from it. ie:
typedef struct _single_tile { TILEFACE Face; TILETYPE Type; TILEFROM From; } TILE, *LPTILE;
typedef struct _tile_flag : public _single_tile { bool Used; } TILEFLAG, *LPTILEFLAG;
The problem is the TILEFLAG AND LPTILEFLAG are underlined in red as if it's an error. |
4 L A T E S T R E P L I E S (Newest First) |
support |
Posted - Jan 27 2009 : 9:22:34 PM case=2302 is fixed in build 1715 |
feline |
Posted - Aug 13 2007 : 08:09:41 AM I sort of get the idea, unfortunately I have found myself in that sort of position as well over the years. You have my sympathies. |
WalderMort |
Posted - Aug 12 2007 : 07:03:49 AM Normally I wouldn't do such a thing, but the first struct is to be tranmitted across the net. On the local machine the struct would then be added to an array and sorted in the most awkward way possible. By adding a boolean and a pointer to the base struct, I can quickly manipulate while the same time being sure each struct is only used once. |
feline |
Posted - Aug 11 2007 : 3:14:47 PM I think this is covered by:
case=2302
out of interest is there some reason why you are deriving a struct from a struct? I know this is valid C++, but most people only do this with classes. |