Annotation of gforth/BUGS, revision 1.19
1.11 anton 1: etags.fs crashes one of my applications (gs.fs). anton 12jan95
1.12 anton 2:
3: not all aliases are in the etags file. Bug in etags.fs? anton 24jan95
1.19 ! pazsan 4: -> wrote special tag generation for cross compilation. bernd 6sep95
1.12 anton 5:
6: emacs often finds the wrong tag. anton 24jan95
1.19 ! pazsan 7: -> emacs does not search for a complete word, but for parts.
! 8: -> Solution: add blanks in front and end of tag name (etags.fs)
! 9: -> and use own forth-find-tag. bernd 6sep95
1.12 anton 10:
1.13 anton 11: gforth.el: indentation does not work right on the first line of a
12: buffer. anton 27jan95
1.19 ! pazsan 13: -> Solved?
1.13 anton 14:
15: Conditional compilation continues after the file ends. This is allowed
16: by the standard (through an ambiguous condition), but the compiler
17: should at least produce a warning. anton 27jan95
1.16 anton 18:
1.19 ! pazsan 19: .1 is interpreted as floating-point number, not as double number or
! 20: error. anton 4may95
! 21: -> All numbers ecvt converts are (by implementation) floating-point.
! 22: -> Should we add a check againgst . at the start of a number?
! 23: -> .1 isn't a double number; it's either an error or a FP number.
! 24: -> bernd 5sep95
1.16 anton 25:
1.19 ! pazsan 26: DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>