My reply is at the bottom. Please put your reply there too.
On Fri, 4 Oct 2019, TK Chia wrote:
Hello Steve, hello David,
SET_WORD(H_FLAGS, z_header.(struct zcode_header_struct)flags);
I am quite sure this change should fix the problem on Turbo C. But it
seems to me that it will also
Shouldn't the `z_header.flags` value just be copied to a `zword` var
and then passed to `SET_WORD( a, v)` to avoid the ambiguity?
Instead of
```
int i;
SET_BYTE(H_CONFIG, z_header.config);
SET_WORD(H_FLAGS, z_header.flags);
```
do
```
int i;
zword zwflags = z_header.flags;
SET_BYTE(H_CONFIG,
Hello Steve, hello David,
SET_WORD(H_FLAGS, z_header.(struct zcode_header_struct)flags);
I am quite sure this change should fix the problem on Turbo C. But it
seems to me that it will also inadvertently break the non-DOS ports,
which do not define SET_WORD in terms of an asm { ... }.
Hi guys,
You have to change line 160 like this:
SET_WORD(H_FLAGS, z_header.(z_header_t)flags);
or
SET_WORD(H_FLAGS, z_header.(struct zcode_header_struct)flags);
How did this work? I used
SET_WORD(H_FLAGS, z_header.(struct zcode_header_struct)flags);
and I got this:
Error
