gforth/BUGS - diff

Return to BUGS CVS log

Up to [gforth] / gforth

Diff for /gforth/BUGS between versions 1.5 and 1.19

-version 1.5, 1994/08/10 17:22:33
+version 1.19, 1995/09/06 21:00:07
  Line 1
- name> does not take the same argument as e.g. .name. Remedy: add cell+
+ etags.fs crashes one of my applications (gs.fs). anton 12jan95
- before name>, but adapt all uses.  anton 23apr94
- revealing the same name several times (e.g., by using refcursive)
+ not all aliases are in the etags file. Bug in etags.fs? anton 24jan95
- results in redefined messages.  anton 28jul94
+ -> wrote special tag generation for cross compilation. bernd 6sep95
- [IF] is case-sensitive.  anton 2aug94
+ emacs often finds the wrong tag. anton 24jan95
+ -> emacs does not search for a complete word, but for parts.
+ -> Solution: add blanks in front and end of tag name (etags.fs)
+ -> and use own forth-find-tag. bernd 6sep95
- gforth.el: fill-paragraph should either not work, or it should make sure that comments stay comments and code stays code.  anton 2aug94
+ gforth.el: indentation does not work right on the first line of a
+ buffer. anton 27jan95
+ -> Solved?
- if blocks.fb does not exist, 1 block creates the file, but cannot
+ Conditional compilation continues after the file ends. This is allowed
- read-file from it. Only if the file-id has been created with
+ by the standard (through an ambiguous condition), but the compiler
- open-file, not create-file, read-file works. - anton 6aug94
+ should at least produce a warning.  anton 27jan95
+ .1 is interpreted as floating-point number, not as double number or
+ error. anton 4may95
+ -> All numbers ecvt converts are (by implementation) floating-point.
+ -> Should we add a check againgst . at the start of a number?
+ -> .1 isn't a double number; it's either an error or a FP number.
+ -> bernd 5sep95
+ DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>

Removed from v.1.5
changed lines
	Added in v.1.19