unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Vorfeed Canal <vorfeed.canal@gmail.com>
Subject: Re: PHP to GUILE
Date: Mon, 26 Sep 2005 12:17:15 +0400	[thread overview]
Message-ID: <6efab23505092601173a0b89b5@mail.gmail.com> (raw)
In-Reply-To: <38294b7405092600273de6d37f@mail.gmail.com>

On 9/26/05, Zeeshan Ali <zeenix@gmail.com> wrote:

> > With a full path to `load-extension' you can put a module anywhere.
> > If your code is a package in its own right then this is a good thing,
> > so you can be certain to get the right file (ie. whatever crazy
> > directory the user might have given).
>
>   Yeah! and you can have a look at the source code of xchat-guile to
> see how exactly thats done:
> http://piipiip.net/~zeenix/xchat-guile-0.2.tar.gz

I took a look. Conclusion: it's a mess.

Why? Easy: guile.so is installed in /usr/lib/xchat/plugins while
plugin-system.scm in installed iin /usr/share/guile/site/xchat-guile.
Ok, if it's in /usr/share/guile/site/xchat-guile then it's guile
extension, right ? Sorry, but no:
guile> (use-modules (xchat-guile plugin-system))

Backtrace:
In unknown file:
   ?: 14* (if (or # #) (try-load-module name))
   ?: 15  [try-load-module (xchat-guile plugin-system)]
   ?: 16  (or (begin (try-module-linked name)) (try-module-autoload name) ...)
   ?: 17* [try-module-autoload (xchat-guile plugin-system)]
   ?: 18  (let* (# # # #) (resolve-module dir-hint-module-name #f) (and # #))
    ...
   ?: 19  (letrec ((load-file #)) (dynamic-wind (lambda () #) (lambda
() #) ...) ...)
   ?: 20* [dynamic-wind #<procedure #f ()> #<procedure #f ()>
#<procedure #f ()>]
   ?: 21* [#<procedure #f ()>]
   ?: 22* (let* ((file #)) (cond (# => #) (# => #)))
   ?: 23  [#<procedure #f #>
"/usr/share/guile/site/xchat-guile/plugin-system.scm"]
   ?: 24  [load-file #<primitive-procedure primitive-load> ...]
   ?: 25* [save-module-excursion #<procedure #f ()>]
   ?: 26  (let (# #) (dynamic-wind # thunk #))
   ?: 27  [dynamic-wind #<procedure #f ()> #<procedure #f ()>
#<procedure #f ()>]
   ?: 28* [#<procedure #f ()>]
   ?: 29* [primitive-load "/usr/share/guile/site/xchat-guile/plugin-system.scm"]
In /usr/share/guile/site/xchat-guile/plugin-system.scm:
   6: 30* (use-modules (xchat-guile main))
   6: 31  (eval-case (# # *unspecified*) (else #))
   6: 32  (begin (process-use-modules (list (list #))) *unspecified*)
In unknown file:
   ?: 33* [process-use-modules (((xchat-guile main)))]

<unnamed port>: In procedure process-use-modules in expression
(process-use-modules (list #)):
<unnamed port>: no code for module (xchat-guile main)
ABORT: (misc-error)

And in this case it's easy to move plugin-system.scm to
/usr/lib/xchat/plugins (where it belongs) since guile DOES have
adjustable %load-path . GUILE does NOT have something similar for
native libraries. That's the problem.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2005-09-26  8:17 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-25 21:50 PHP to GUILE Vorfeed Canal
2005-09-26  1:42 ` Kevin Ryde
2005-09-26  7:27   ` Zeeshan Ali
2005-09-26  8:17     ` Vorfeed Canal [this message]
2005-09-26 17:57       ` Zeeshan Ali
2005-09-26 19:05         ` Vorfeed Canal
2005-09-26 19:34           ` Zeeshan Ali
2005-09-26  7:43   ` Vorfeed Canal
2005-09-26 11:17     ` Thien-Thi Nguyen
     [not found]       ` <6efab23505092609331abd82b7@mail.gmail.com>
2005-09-26 16:34         ` Vorfeed Canal
2005-09-26 22:12           ` Thien-Thi Nguyen
2005-09-27 10:11             ` Vorfeed Canal
2005-09-27 12:48               ` Thien-Thi Nguyen
2005-09-27 14:36                 ` Vorfeed Canal
2005-09-27 17:13                   ` Thien-Thi Nguyen
2005-09-27 17:47                     ` Vorfeed Canal
2005-09-27 19:44                       ` Thien-Thi Nguyen
2005-09-26 12:23 ` Exceptions Ludovic Courtès
2005-09-26 19:20   ` Exceptions Vorfeed Canal
2005-09-27  8:42     ` Exceptions Ludovic Courtès
2005-09-27 10:54       ` Exceptions Vorfeed Canal
2005-09-27 15:45         ` Exceptions Ludovic Courtès
2005-09-27 17:18           ` Exceptions Vorfeed Canal
2005-09-28  7:10             ` Managing Guile and extensions versions Ludovic Courtès
2005-09-28 20:19               ` Vorfeed Canal
2005-09-29 15:34                 ` Ludovic Courtès
2005-09-29 16:30                   ` Vorfeed Canal
2005-09-30 22:07                     ` Neil Jerram
2005-10-19  7:58                       ` Rob Browning
2005-09-29 22:24               ` Kevin Ryde
2005-09-30  8:00                 ` Ludovic Courtès
2005-10-02  1:59                   ` Kevin Ryde
     [not found]                     ` <6efab2350510020425j76899e29hec6ea7e3dcce6c3@mail.gmail.com>
2005-10-03  1:58                       ` Kevin Ryde
2005-10-04 11:06                         ` Vorfeed Canal
2005-10-04 23:58                           ` Kevin Ryde
2005-10-05 14:18                             ` Vorfeed Canal
2005-10-09  1:53                               ` Kevin Ryde
2005-10-11 10:20                                 ` Vorfeed Canal
2005-10-11 14:56                                   ` Greg Troxel
2005-10-11 21:32                                   ` Kevin Ryde
2005-10-03 12:58                     ` Ludovic Courtès
2005-09-26 19:37 ` PHP to GUILE Neil Jerram
     [not found]   ` <6efab235050926131843ce69e2@mail.gmail.com>
2005-09-26 20:18     ` Vorfeed Canal
2005-09-26 22:39       ` Kevin Ryde
2005-09-27  9:20         ` Vorfeed Canal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6efab23505092601173a0b89b5@mail.gmail.com \
    --to=vorfeed.canal@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).