Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


cgi and forth

cgi and forth

cgi and forth

anyone got cgi working with forth?

forth seems ideal because cgi always has problems with too little memory on the computer, and forth uses little to get work done...

RE: cgi and forth

I had to look up "cgi", but I remember a little about FORTH.

FORTH uses little code space for executables, and grows slowly with program size, mostly because of intensive re-use of tiny atomic functions.

I'd imagine that cgi would have memory problems because of the requirement to process, store, and cache, large numbers of long strings.

If I'm understanding the problem correctly, I don't think FORTH would bring much to the party, because the strings would still be long and numerous.  Reducing the size of the code to zero (which is effectively what FORTH does relative to equivalent current scripting languages), would just free up that much memory.

Or, I could be wrong; it happens regularly.

RE: cgi and forth

Interesting; has anyone ever tried to reduce the strings? say  numbering words from 1 to 10,000 and replacing all the words with numbers the machine can easily deal with.  Then having the client cache this mapping, then letting the machine be blindingly fast...?? (theory heavy here)

RE: cgi and forth

You could compress the strings, but you'd pay heavily in execution time for decompression for all but the simplest compression, e.g. run length encoding.

You'd lose more speed by doing it in FORTH; most dialects are slower at run-time than the binaries produced by a C compiler.  The speed penalty comes from the tiny tight loop that's responsible for much of FORTH's power and code density; the inner interpreter.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close