Re: [gforth] problem with gforth7 and serial access

[kibler]

Thanks for the response - I will look into using the crontrib/serial.fs
as it looks pretty well complete. Maybe I can follow what serial.fs
does as such and figure out what is broke in 7.0.

The problem is that contrib is not part of gforth-0.7.0+ds1
the release version of Debian testing. I see lots of extra tools
in 0.7.9 that might help, but as of now, I think you can only
get those by cloning the repo and building it on your machine.
That is a step we would rather not have the users do.

I will try later today to see if serial.fs works on 0.7.0, as I have
previously tried similar options only to find them calling many
other un-loaded words. That is one of the concerns of working
with multiple versions, that not all words work on all versions.

Thanks again for your comments.
Bill.


On 03/22/12 01:32, David Kuehling wrote:
> > Greetings:
> > This will take a bit to cover, so please read all before responding.
> > I work with several others and we have been using gforth version
> > 0.6.2, for many years. We use it to create and develop the myforth
> > 8051 macro forth compiler and programs for the SiLabs devices. It has
> > worked just fine for many years and still works even on Debian testing
> > systems - the latest versions of stable programs.
> > Over the years we have tried gforth version 7.0 and the serial code
> > that worked well on 6 fails. Version 7.0 is the current release that
> > most linux distributions ship. I have recently cloned the
> > gforth-mirror repo and the gforth version 0.7.9 fails with the serial
> > code.
> Have you had a look at contrib/serial.fs in the gforth distribution?
>
> http://www.complang.tuwien.ac.at/cvsweb/cgi-bin/cvsweb/gforth/contrib/serial.fs?rev=1.2;content-type=text%2Fplain
>
> while this may not be the same API as you're using, porting your code
> over to using it will reduce some of the headaches that come with
> providing your own serial port code?
>
> cheers,
>
> David