Re: SEAforth Instruction Set

This is a message from a lone wandering Forth programmer who just
stumbled upon this thread while looking for the SeaForth instruction
set.

I am utterly disgusted by the behavior of all of you towards Mr. Jeff
Fox, your total irreverance towards all that he and Intellasys is
doing, and your useless speculations. This isn't productive. I feel
sorry for Jeff for having to defend himself so violently but I can
relate to the kind of onslaught that common programmers can pose to
real Forth programmers.

Anyway it doesn't matter. I've gotten the picture (correct me if I'm
wrong, Jeff) from reading the first 1/2 of the thread that Jeff is
talking around the assumption that we all should have realized by now
that documentation CAN'T be given right now because the system is not
finished. In the traditional form, the Forth/hardware combination is
constantly evolving til the very end. You never know what kind of
kinks come up that can be worked out or lead to new innovations.

The most interesting part about the SeaForth chip, to me, is not its
silly old instruction set, all of that is relatively superficial, and i
feel, has a very specific purpose of illustrating what a machine forth
32-instruction set would look like for a parallel processor. I saw it,
and I was a little intrigued, but I moved on. If you're working on
anything worthwhile, you wouldn't CARE what p!+ is really for, because
you are NOT IN THAT WORLD YET. Personally, I sought the instruction
set out because I just recently considered caching the top of my return
stack in a register and I thought "what kinds of new instructions could
take advantage of this?" and maybe you can put together the rest. The
point was, what is already being done in a context similar to mine,
that I can leverage? And I didn't find anything so I will probably
just have to find out through my work if the register will be used in
some new instructions.

I think that speculation is fun, a great social activity. Great for
coming up with your own ideas - in your own sphere. There is a
horrible illusion we have today that the world has vaguely been united
by the internet. And over the course of a couple decades - neat! But
why do you want to speculate about something that is not up to you to
ever decide? It only colors your opinion once you see the final thing,
giving you false reference for judgements. SeaForth is not so
important that everyone absolutely has to know what the instruction
set is before it is even available. What are you goign to do, write
PROGRAMS for it before you even have one??

.

Relevant Pages

  • Re: SEAforth Instruction Set
    ... I am utterly disgusted by the behavior of all of you towards Mr. Jeff ... The most interesting part about the SeaForth chip, to me, is not its ... silly old instruction set, all of that is relatively superficial, and i ... stack in a register and I thought "what kinds of new instructions could ...
    (comp.lang.forth)
  • Re: [repost]Eorros for me, in the assembly history
    ... > 1) Do not use multiple instruction for line ... Even *RosAsm* programmers do this. ... I think you're confusing "assembly language programmers" with ... > 7) Do not use heavy "heap memory" and the memory control functions ...
    (alt.lang.asm)
  • Re: A Disassembly Problem for Rene to Consider
    ... A disassembler can do likewise, emulate the state-machine, ... > where programmers would bury a two-byte instruction inside ... > the three-byte LXI instruction. ...
    (alt.lang.asm)
  • Re: anyone interested in decompilation
    ... programmers have access to, certain code such as the bios and some ... It's very rare that a decompiler would output inline asm though. ... possible to generate C code this simulates the instruction pointer. ... In Boomerang we recognise these and decode ...
    (alt.lang.asm)
  • Re: Am I programming correctly with array parameter?
    ... Nice instruction set but glacially slow by today's standards. ... from quite a few x86 compilers and have seen nearly ... certain there are more active assembly language programmers today than ...
    (alt.comp.lang.learn.c-cpp)
Loading