From: Zeeshan Ali <zeenix@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: PHP to GUILE
Date: Mon, 26 Sep 2005 22:34:56 +0300 [thread overview]
Message-ID: <38294b7405092612341caa90f8@mail.gmail.com> (raw)
In-Reply-To: <6efab23505092612053fe5b4e8@mail.gmail.com>
Hello again,
> > Your conclusion is based on your ignorance.
> >
> Possible. Care to enlighten men ?
I already did but you seem to be too eager to prove your point.
> Ok. And then why your plugin-system never loaded this main module instead ?
Because i'ts the opposite, the maim module actually loads the
plugin-system module. Please read the source, which is only one C
file.
> Ok. No problem. If this "is NOT an xchat plugin" but simple guile
> module then it usable without xchat, right ?
I didn't say that it's not related to xchat or the xchat-plugin
that needs this module.
> This means (use-modules
> (xchat-guile plugin-system)) works, right ? Oops. It does not.
> Conclusion: it's NOT guile module but part of xchat module.
You seem to be very eager to derive conclusions. Your problem seems
to be that you are making it an either/or situation (i-e either it's a
'pure' and 'independent' guile module or it's a pure and independent
xchat plugin), which is not the case here.
> It's
> written in scheme but it does not make it guile module. Just like the
> fact that your guile.so is written in C does not make it C library.
In my last email i explicitly declared the main-module to be writen
in C, so i am obviously not assuming anything like that.
> > Since it's a guile module, IMHO it doesn't belong in directory for xchat plugins.
> >
> But it's NOT guile module - my simple test proved it. That's the problem.
And i proved your test to be based on ignorance, perhaps you are
better off coding in PHP. :) Anyway, thats my last email, if you dont
get it this time either, stop calling my hard-work 'a mess'.
--
Regards,
Zeeshan Ali
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-09-26 19:34 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
2005-09-26 17:57 ` Zeeshan Ali
2005-09-26 19:05 ` Vorfeed Canal
2005-09-26 19:34 ` Zeeshan Ali [this message]
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=38294b7405092612341caa90f8@mail.gmail.com \
--to=zeenix@gmail.com \
--cc=guile-user@gnu.org \
/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).