On Thu, May 10, 2001 at 05:20:46PM -0300, Daniel C. Sobral wrote:
John Sadler is not a Unix user, and has no experience with Unix, and
...
If you know exactly how to produce a .tar.gz under Windows that is
suitable for our use, I'm sure he would appreciate the help.
Ask him to use
On Thu, May 10, 2001 at 02:21:09AM -0300, Daniel C. Sobral wrote:
John Sadler is not a Unix user, and has no experience with Unix, and
...
If you know exactly how to produce a .tar.gz under Windows that is
suitable for our use, I'm sure he would appreciate the help.
Ask him to use
On Thu, May 10, 2001 at 02:21 -0300, Daniel C. Sobral wrote:
John Sadler is not a Unix user [ ... ] If you know exactly how
to produce a .tar.gz under Windows that is suitable for our
use, I'm sure he would appreciate the help.
Most of the distros I've seen (Linux as well as *BSD) have the
David O'Brien wrote:
On Thu, May 10, 2001 at 02:21:09AM -0300, Daniel C. Sobral wrote:
John Sadler is not a Unix user, and has no experience with Unix, and
...
If you know exactly how to produce a .tar.gz under Windows that is
suitable for our use, I'm sure he would appreciate the help.
For anyone who writes their own FORTH in the loader scripts:
ficl 2.05 (imported on 28th April by dcs) changes `base' from an
lvalue to an rvalue. This will break any code that currently
uses base. In particular, code to temporarily change the base
will corrupt low memory. For example:
Peter Jeremy wrote:
For anyone who writes their own FORTH in the loader scripts:
ficl 2.05 (imported on 28th April by dcs) changes `base' from an
lvalue to an rvalue. This will break any code that currently
uses base. In particular, code to temporarily change the base
will corrupt low
Daniel C. Sobral wrote:
I have no idea why this change was made - it breaks FORTH compatibility.
I can't find anything in ficl.sourceforge.net (except that someone has
helpfully stripped all the CR's off ficl205.tar before it was gzip'd -
which upsets tar quite a bit).
John Sadler is
