Hi Enoch,
> There's a reason for my asking. When I try to merge your new VALUE
> implementation with my repository things stop working... The previous
> implementation worked for me just fine.
What has really changed is the parameter for the fetch/store
methods inside of the values. That has cha
Hello Matthias,
Matthias Trute writes:
>> 2. Can you please briefly explain the recent changes concerning values?
>>f75ab2c * Variations of VALUE
>>1bb0e1a * Finalize the API changes for VALUEs
>>435621c * New internal API for values.
>
> Make the documentation and the working feature
Hi Enoch,
> 1. In amforth-eeprom.inc line #1:
>.dw -1 ; EEPROM Address 0 should not be used
>What use does the first cell serve?
At least some atmega controller types explicitly stated in
the data sheets that the first eeprom address may get corrupted
for various reason. I never
Hello Matthias,
1. In amforth-eeprom.inc line #1:
.dw -1 ; EEPROM Address 0 should not be used
What use does the first cell serve?
2. Can you please briefly explain the recent changes concerning values?
f75ab2c * Variations of VALUE
1bb0e1a * Finalize the API changes for VAL
