Re: [Amforth] imove

2013-04-14 Thread Enoch
Matthias Trute writes: > Hi Enoch, > >> In your latest docs you refer to having a GIT tree, where is it based? > > Its on my local desktop system. Not available for external access. > >> I would like to track AmForth via GIT rather than SVN for some local >> kernel changes that I maintain (*) > >

Re: [Amforth] imove

2013-04-13 Thread Matthias Trute
Hi Enoch, > In your latest docs you refer to having a GIT tree, where is it based? Its on my local desktop system. Not available for external access. > I would like to track AmForth via GIT rather than SVN for some local > kernel changes that I maintain (*) I've heart that git-svn works well. N

Re: [Amforth] imove

2013-04-12 Thread Enoch
Matthias Trute writes: > Thanks for sharing. Fix applied :=) Hello Matthias, I really enjoy the experience and I should be thanking you! In your latest docs you refer to having a GIT tree, where is it based? I would like to track AmForth via GIT rather than SVN for some local kernel changes th

Re: [Amforth] imove

2013-04-12 Thread Matthias Trute
Hi Enoch, > I had it fixed for my own use, so here sharing: Thanks for sharing. Fix applied :=) Matthias -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The plat

Re: [Amforth] imove

2013-04-11 Thread Enoch
Matthias Trute writes: >> Also, it seems to me that your implementation may cause ram buffer >> overflow. > > The code copies flash cells. That may overrun the > RAM if an odd number of bytes is transferred. Thats > bad indeed. Hello Matthias, I had it fixed for my own use, so here sharing: :

Re: [Amforth] imove

2013-04-11 Thread Rafael Gonzalez
mmm ... I think the 200x proposal misses EEPROM as Data space  De: Matthias Trute Para: Everything around amforth Enviado: Miércoles 10 de abril de 2013 20:58 Asunto: Re: [Amforth] imove Hi, > May I suggest renaming the new implementation of imove &g

Re: [Amforth] imove

2013-04-10 Thread Matthias Trute
Hi, > May I suggest renaming the new implementation of imove > ( i-addr len ram -- ) at lib/ans94/core/imove.frt to icmove: Uhm. The naming I'd like to delay. There are some efforts to get a consistent naming convention for memory accesses. One example is http://www.forth200x.org/memory-2010-06-2

[Amforth] imove

2013-04-07 Thread Enoch
Hello Matthias, May I suggest renaming the new implementation of imove ( i-addr len ram -- ) at lib/ans94/core/imove.frt to icmove: imove should be a variant of move, that is: "copy the contents of u consecutive address units". icmove should be a variant of cmove, that is: "copy u consecutive ch