At 10:56 PM +0200 on 4/7/00, M. Uli Kusterer wrote:

> Hmmm... could we probably store this in some config-file-like storage? If
>you had something like ResEdit's TMPL editor for these, we could provide a
>simple UI to edit stuff like this. Oh well, we'll find a way to achieve
>this.

Let me try once more to get the full magnitude of what I'm actually
planning of allowing in an efficient interpreter across: Dynamic
rewriting of the syntax at runtime.

You put those commands I showed in a script somewhere. They add the
specified syntax to the FreeScript language.

You could have a system-wide syntax addition in the Home stack, of course.

Here is an example, from a future FreeWeb web browser. Note that you
can even add to builtins like this. It is _very_ powerfull, to say the
least!

on openstack
  get Add Command
    1: "go" <url>
    2: "go" <url> in new window
  With "url" being one word of
      "http://" <STRING>
      "ftp://" <STRING>
      "gopher://" <STRING>
  With FreeTalk for 1
    FreeWebGo(param(1), false)
  With FreeTalk for 2
    FreeWebGo(param(1), true)
  set the GoCommandReference of me to it
  pass openstack
end openstack

on closestack
  Remove Command (the GoCommandReference of me)
  pass closestack
end closestack

[I'm playing with the syntax -- comments are welcome]

> Ummm... I'd hate to have to rely on other applications, especially as I
>doubt all Unix or Linux computers have a compiler installed. I know most
>Linuxes ship with one, but I'd guess the average SysAdmin in a company
>would just leave it out to save disk space.

Doubtfull. You can't (really) use a Unix box without a linker, because
on Unix, you are given source code, not binaries for most everything
(unless you happen to use RedHat 6.1/Inhel and trust whomever made the
RPM)
                    ^
            that's not a typo


Reply via email to