On 10/13/2012 02:53 PM, Matthias Trute wrote:
> Hi,
>
>> We do still have a problem how to deal with hardware idiosyncrasies as
>> timer0.frt demonstrates. It should not be dealt with through the shell
>> (re my ill thought #py idea).
>>
>> The generic frt code should include some preprocessing in
Hi,
> We do still have a problem how to deal with hardware idiosyncrasies as
> timer0.frt demonstrates. It should not be dealt with through the shell
> (re my ill thought #py idea).
>
> The generic frt code should include some preprocessing instructions to
> produce MCU specific code, m4 perhaps?
On 10/13/2012 11:29 AM, Matthias Trute wrote:
> Hi,
>
>> What is your recommended practice?
>
> Very simple: Use what you like most. All tools
> that I include with amforth are the ones I consider
> useful for others as well. I do not enforce any of
> them.
>
> The shell has a few advantages ove
Hi,
> What is your recommended practice?
Very simple: Use what you like most. All tools
that I include with amforth are the ones I consider
useful for others as well. I do not enforce any of
them.
The shell has a few advantages over a dumb terminal
and I like to use it. YMMV.
Matthias
--
