Re: PHP to GUILE

[Vorfeed Canal]

On 9/26/05, Thien-Thi Nguyen <address@hidden> wrote:
>    From: Vorfeed Canal <address@hidden>
>    Date: Mon, 26 Sep 2005 11:43:59 +0400
>
>    This means I'm not the only one who feel like this hardcoded path is
>    not a good solution.
>
> you may be able to get guile 1.4.x[1] to do what you want.  all the
> compiled modules (shared object libraries following a certain loading
> convention) of Guile-SDL and Guile-PG, for example, are not installed
> under /usr/local/lib.
>

And they are incompatible with pthreads and are not using GOOPS at
all. Thnx, but no thnx.

> those packages use "module catalogs", which is another (IMHO superior)
> resolution mechanism, but anyway guile 1.4.x provides `%%ltdl' to expose
> low level (prefix-path-munging) mechanisms from libltdl, should you
> prefer that kind of control.
>

Hmm... And why "module catalogs" are superior ? I see one reason for
their existence, but may be there are ones. For example I view this
feature: "the actual placement of the file in the filesystem is
decoupled from its module name" as DISadvantage... I mean: we need
hierarchy of modules, we have perfect system to organize objects in
hierarchy called "filesystem" why we'll ever want to replace it
without very compelling reasons?

> (hmmm, i just checked to see if there are online docs for `%%ltdl', but
> there aren't (yet), so i will write some shortly and post a link in
> another message -- in the meantime, you can look at the source file
> guile-1.4.1.106/libguile/lt.c for ideas.)

The biggest problem with this mechanism is that it's unsupported by
official version. I can as well just go back to PHP and revert
unneeded changes. After all I was able to revert this:
http://cvs.php.net/diff.php/ZendEngine2/zend_execute.c?r1=1.652.2.38&r2=1.652.2.39&ty=u
and now my old PHP scripts are Ok. I want STABLE SUPPORTED language,
not something I'll be destined to keep in working state myself.