gforth/doc/gforth.ds - diff

Return to gforth.ds CVS log

Up to [gforth] / gforth / doc

version 1.208, 2009/12/31 15:32:35	version 1.209, 2010/03/05 14:28:13
Line 1324 given here in upper case.	Line 1324 given here in upper case.
@node Crash Course Tutorial, Stack Tutorial, Syntax Tutorial, Tutorial	@node Crash Course Tutorial, Stack Tutorial, Syntax Tutorial, Tutorial
@section Crash Course	@section Crash Course

Type	Forth does not prevent you from shooting yourself in the foot. Let's
	try a few ways to crash Gforth:

@example	@example
0 0 !	0 0 !
Line 1333 here execute	Line 1334 here execute
' (quit) >body 20 erase	' (quit) >body 20 erase
@end example	@end example

The last two examples are guaranteed to destroy parts of Gforth (and	The last two examples are guaranteed to destroy important parts of
most other systems), so you better leave Gforth afterwards (if it has	Gforth (and most other systems), so you better leave Gforth afterwards
not finished by itself). On some systems you may have to kill gforth	(if it has not finished by itself). On some systems you may have to
from outside (e.g., in Unix with @code{kill}).	kill gforth from outside (e.g., in Unix with @code{kill}).

	You will find out later what these lines do and then you will get an
	idea why they produce crashes.

Now that you know how to produce crashes (and that there's not much to	Now that you know how to produce crashes (and that there's not much to
them), let's learn how to produce meaningful programs.	them), let's learn how to produce meaningful programs.