![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
http://en.wikipedia.org/wiki/Ch_interpreter
http://www.softintegration.com/
yep, now it's truly portable... :P
eager to script in C? :))
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis schrieb:
> eager to script in C? :))
I must say that - um, no, actually not :-P
(Wait - hey, it's an embedded scripting language... I have an idea -
let's use C as the POV-Ray 4.0 SDL... >_<)
(*shouts "YEHOVAH!"*)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
clipka escreveu:
> nemesis schrieb:
>> eager to script in C? :))
>
> (Wait - hey, it's an embedded scripting language... I have an idea -
> let's use C as the POV-Ray 4.0 SDL... >_<)
all bow before almighty C! :P
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis wrote:
> yep, now it's truly portable... :P
While not portable, sophisticated commercial C interpreters have been around
since 640K was a lot of memory. Just so's ya know.
--
Darren New, San Diego CA, USA (PST)
Understanding the structure of the universe
via religion is like understanding the
structure of computers via Tron.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New escreveu:
> nemesis wrote:
>> yep, now it's truly portable... :P
>
> While not portable, sophisticated commercial C interpreters have been
> around since 640K was a lot of memory. Just so's ya know.
oh! Didn't know that. Such a crazy idea, after all... what's the point
when it's clearly not well suited for quick scripting, nor to performant
code, specially in the face of C compilers for virtually all
architectures under the sun?
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis wrote:
> oh! Didn't know that. Such a crazy idea, after all... what's the point
The point was that when your link takes 45 minutes and a full recompile
takes 4 hours, you build your lower-level libraries once, link them into the
interpreter, and then develop the next layer of functionality in the
interpreter until you're ready to compile *that* layer.
I.e., it was really more useful as a REPL sort of thing than anything in
production. Plus, IIRC, it did things for you like looking for buffer
clobbering and such, if you told it to. And allowed breakpoints and all
that stuff. But mainly I used it to avoid the overhead of compile and link
during development.
--
Darren New, San Diego CA, USA (PST)
Understanding the structure of the universe
via religion is like understanding the
structure of computers via Tron.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |