IDE Idea, was Forth in 3D, Say Hello, ...


    Sponsored Links


  • 1. ALLOCATE, good test.
    Has anyone a good test for the memory allocation? E.g. some generating ALLOCATE's and FREE's in a frequency based on some pattern plausibly related (even remotely) to real world applications? Groetjes Albert

IDE Idea, was Forth in 3D, RE: Say Hello, ...

Postby mawcowboyusa » Wed, 01 Oct 2003 09:39:01 GMT

Forth in 3D

Say Hello, ...

silk, scheme in 50k, progammed for java virtual machine ( JVM 1.1)
or  http://www.**--****.com/ 

treemaps, a demonstraction of a techinquie for displaying word
( word network process wysiwig view modle for visual programming )
 http://www.**--****.com/ ~bulatov/HyperProf/
oh, what the heck, thrill yourself today with an Java Applet demo.

for network of network ( parallel process) connections subtypes , 
jcsp, the Quickstone version, which
needs a (small) commercial licence and includes the Networking Edition


then simply for fun simulate the any forth machine code in java.
( myForth forth machine code simulations or
 http://www.**--****.com/ ) ( for
FORTH in Javav cross compilers for *REAL* machine code downloaded
to-site for test simulations )

the first two pieces of information can build a real cool visual 
program builder ide, maybe in Scheme or UML for logic, what jcsp may 
allow is icing on the ease of progamming and 

I look forward to your discerned comment


64 bit is shit for memory chip investment 
Intel rules with internal multi threading ( SMP inner chip )
what bit is six{*filter*} ( 16) six{*filter*}-bit in parallel access of DRDRAM?
( design note : my balace of variable predicted a 64-bit total IP
cache size
for my 16-bit instrction, nice for 5-bit encoded branch of 64-bit
boundary of
16 bit instructions ( 128 length for 16-bit ( word size) short branch)
( oh ya 32-local registers, plus 32-micro theory /local method 5-bit
packed )
32-deep-word to page over/underflow fault , 3 packed five bit (
redirect decode ( like in 16-bit vs-32 in ARM only 16-bit vs three
5-bit in
my design model ) )

IDE Idea, was Forth in 3D, RE: Say Hello, ...

Postby mawcowboyusa » Wed, 01 Oct 2003 09:56:02 GMT

( 16bit vs three 5-bit programmable to 16 bit, ok talk with
Washington, I official recommended a procedure )

Similar Threads:

1.Hello i am new to this C programs

const struct
   float a0;
   float a1;
   float a2;

i am confused to declare the value for this structure correct me

i have declared this there is compiler error

2.Hello I am Barnie

Just taking the time to introduce myself. Computers are great and I
spend most of my time on it. Have lots of stuff to share and I hope
you benefit from them. Ok well that is that... mmmm.... yeah...

3.C vs Forth vs whatever Executables for Hello World

In a recent thread in comp.arch.embedded entitled "Where does C++
fit in?" some people were comparing executables for C and C++
for Hello World examples.

Now I know a .COM file in DOS can do it in <30 bytes.  But I
was supprised to see the size of the executables generated
by C and C++ (presumably for a Linux system (and in a thread
about where C++ fits into embedded system use).

Those numbers ranged from about 2700 to 388,000 ( -static)
after the application of -strip. With -static and before
-strip the size was a whopping 1.7M.

Now I know that TCOM when targeting for DOS produces a .COM
of ~300 bytes.  I wonder if any other optimizing target
compiles produce smaller code, closer to the <30 bytes
required for a .COM using DOS function call.  Does anyone
have numbers smaller than 300?

The ~300 for TCOM is about a 10/1 overhead, the 2700 for
GCC and G++ (presumably for a Linux target but I don't know)
is more like a 100/1 overhead.  The 388,000 and 1.7MB 
numbers just seem to have too much overhead to believe.

If you include the 30K or 50K DOS OS code needed, or the
Linux OS overhead the numbers are much bigger.  What
are the smallest executables that people's target
compilers generate for Hello World programs?

Best Wishes

4.Forth and Prolog (Was: Executables for Hello World)

5.VFX Forth for Linux and hello world


just started to play with VFX Forth for Linux.

It's an old tradition to start with the hello world program.

I wrote hello.fs
   : main ." Hello VFX-World!" cr ;
   assign main to-do entrypoint
   save hello.elf

Then spend some time figuring out if vfxlin has some support for
command line arguments and finally compiled with
   vfxlin "include hello.fs" && mv hello.elf hello

The produced executable was working but 'file hello' report this
   hello: ELF 32-bit LSB executable,
   Intel 80386, version 1 (SYSV),
   dynamically linked (uses shared libs),
   corrupted section header size      <-- strange !?

I missed something or do something wrong in my ompilation command?


6. What do you mean saying 'FORTH'?

7. Availability of assemblers C vs Forth vs whatever Executables for Hello World

8. forth on multi core liek say i7

Return to forth


Who is online

Users browsing this forum: No registered users and 53 guest