3.204 & 3.205 Bug (part 1)

[Futureatwork]

C-H Wu:

[ckielstra]

In order to retrieve the high or low byte of an int16 xpercad started with the following code:

[Hans Wedemeyer]

If your code can tolerate one global variable for the Address then it will only require ONE byte to load the High or Low parts of the Address.

// struct to enable easy access to high and low byte
struct HighLow
{
char l;
char h;
};

typedef union HL_TAG
{
long L;
struct HighLow hl;
}HL16;

HL16 g_Address; // the global address for

void write_ext_eeprom( byte data)
{
byte low_byte, high_byte;
// I have no idea what the orginal user wanted to do with these. Of course the two bytes are not needed. Simply use the g_Address.hl.l and g_Address.hl.h directly, it saves even more space... can I then claim 0 Bytes... :-)

low_byte = g_Address.hl.l; // 1 byte
high_byte = g_Address.hl.h; // 1 byte
}


void main()
{
int data=0;

g_address = 32000;
write_ext_eeprom( data);

}


From the LST
.................... void write_ext_eeprom( byte data)
.................... {
.................... byte low_byte, high_byte;
....................
.................... low_byte = g_Address.hl.l; // 1 byte
0004: MOVFF 05,09
.................... high_byte = g_Address.hl.h; // 1 byte
0008: MOVFF 06,0A
.................... }
000C: GOTO 002C (RETURN)
....................

[C-H Wu]

It is great to know that there are quite a few different ways to do the job!

Here is CCS's reply to xpercad's e-mail:

[C-H Wu]

Hi, Futureatwork:

[ckielstra]

Hi Hans,

[Guest]

[C-H Wu]