> www.BLOCKPROLOG.comis written in PHP.
>
> I'm thinking of just allowing the PROLOG PROGRAM to shell back down to
> PHP.
>
> public static function test() {
> $args = func_get_args();
> echo static::NAME, " ".join(',', $args)." \n";
> }
>
> This is a bit like EVAL( 'function-in-a-string' ) in LISP.
>
> This would cut down my work in doing add on modules...
>
> e.g. to WRITE text the PROLOG code would be..
>
> test X :-
> PHP echo X
>
> So you could effectively do anything that PHP does within
> BLoCKPROLOG.com!
>
> Herc
Yeh so I think you want an INTERPRETED PROLOG to do this.
Interpreted languages can run any commands on that system on the fly.
<?php
// outputs the username that owns the running php/httpd process
// (on a system with the "whoami" executable in the path)
echo exec('whoami');
?>
<?php
exec("/usr/bin/secureprogram password");
?>
PHP-PROLOG calls PHP-command
PHP-commands calls UNIX commands
Something like:
unix COM :-
PHP exec('usr/bin/' . COM . ');
is DO-ABLE in a scripted PROLOG.
-----------------
It wouldn't be wise to allow this control from BlockProlog.com
on my shared Web Host!
maybe if BlockPROLOG gets to the CMS website development stage...
Herc
--
www.BLoCKPROLOG.com