30 Jan
2006
30 Jan
'06
3:03 p.m.
In article <200601301749.01430.rtellason at blazenet.net>,
"Roy J. Tellason" <rtellason at blazenet.net> writes:
On Monday 30 January 2006 02:03 pm, Richard wrote:
I believe the FORTH philosophy is that you should write your own I/O
WORDs that make sense for your application. The console I/O stuff is
only there because FORTH is intended to be an interactive environment
(at least for development). You mean your target system doesn't even
have a serial port?
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>
In article <200601301050080652.435B73FC at
10.0.0.252>,
I'd say that's accurate. FORTH was designed for microprocessor
control in embedded systems. People have added all kinds of layers on
top of the kernel over the years, but its typeless nature gets kind of
grungy in larger applications.
In spite of what I hear about it being designed for that kind of app
(originally for telesscope control?) the stuff I've gotten so far seems to be
remarkably weak in terms of i/o operations, with a LOT (way too much) being
devoted to console-I/O type stuff. Which doesn't help a whole lot when you
don't have a console...