gmane.lisp.scheme.gambit

Re: location of libgambcgsi.so

Marijn Schouten (hkBst — 2008-12-01T22:34:52

_______________________________________________ Gambit-list mailing list Gambit-list< at >iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

Re: Adding docs to wiki?

vasil — 2008-12-01T21:03:22

Greetings! I am very interested in Gambit-C, because of using it in my project. Very like it for the relative simplicity and good design. And I would like to support it according to my abilities. type_of_described_object___object_name - is reasonable for the first-time choice. Procedure_getenv - sounds good. And thoughts about integration with IDE are good too. It will be great if whole documentation have strong hierarchical structure. For instance: |---Data types | | | |-----Numbers | | |---Intro | | |---Exact/Inexact | | |---Fixnum/Flonum | | |---Numeric functions | | |---Conversion | | |---Math operations | |-----Lists | |-----Vectors ... and so on So, IMHO navigation through pages should consist of next links: same level articles navigation: << prev next >> (Intro <-> Exact/Inexact<->Fixnum/Flonum) Up level: ^Up Jump to topic: ^Numbers Jump to root: ^Contents Links to relative information: See also: Links to some other stuff like discussion threads. Some good ideas of navigation could be found in CLHS ( Common Lisp HyperSpec) There are few things I'd like to point to: May be introduce different fonts for different items, to improve readability? For instance: in "...(getenv name [default]).." I suggest to use italic font for variables and optional values and to make text size larger of other text. And it will be good to use some tags for color marking of text pieces. This will help to make accents on important information. I think there must be only one, who is responsive for decision which documentation to copy back. Try to guess, who... :) And I also think, that every change in documentation, source code and so on, should go to the final version of Gambit-C via main developer. Main developer is responsive for keeping good and simple design of project, including documentation and build system. Take look what is happening with sbcl now: enormously big, weird and very hard to understood and maintain. And there is no vector to simplify it and reduce its complexity, because of absence of main architect.

Re: Adding docs to wiki?

Marc Feeley — 2008-12-01T18:46:17
I looked into what was necessary to write a Texinfo plugin for MediaWiki (which is used by the Gambit wiki). It turns out to be simpler than I thought. So I wrote a plugin which handles ...Texinfo document... in any wiki page. The plugin calls up texi2html to convert the Texinfo document to HTML (currently everytime the page is accessed). Here are 3 pages written with the tag: http://dynamo.iro.umontreal.ca/~gambit/wiki/index.php/Procedure_getenv http://dynamo.iro.umontreal.ca/~gambit/wiki/index.php/Procedure_current-time http://dynamo.iro.umontreal.ca/~gambit/wiki/index.php/Special_form_time Go to one of these pages and click on "edit" to see what the source document looks like. The Texinfo document is wrapped inside and tags. I'd like to get some feedback on these pages before I put the rest of the Gambit manual on the wiki. Some issues: 1) What name should the pages have? I use the Procedure_ and Special_form_ prefixes so that a name can easily be found. But perhaps it is better to have a unique prefix (Documentation_of_ or simply nothing, but this might cause a name clash) so that the page can be accessed directly without knowing if the name refers to a procedure or a special form. This would make the wiki documentation easy to access from an IDE. I can easily imagine the IDE adding to the error messages a hyperlink to the wiki documentation of the procedure which raised the exception. 2) Where should the documentation which is outside the Texinfo < at >deffn forms be put? For example, general discussion of I/O, or debugging, or the compiler, general index, concept index, etc. 3) How should hyperlinks work within the wiki? 4) Can the HTML's prettiness be improved? 5) How can the wiki documentation be copied back to the Gambit manual? When should this happen? Marc On 30-Nov-08, at 2:31 PM, Ali wrote:

Can't use make update

Bradley Lucier — 2008-12-01T04:56:11
This doesn't work (from history): It fails with

Re: location of libgambcgsi.so

Marijn Schouten (hkBst — 2008-11-30T15:53:47
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc Feeley wrote: Hi Marc, I guess you need to decide whether DESTDIR support is more valuable, than having to have wrapper scripts that set LD_LIBRARY_PATH on some obscure platforms. Of course this does not mean you HAVE to use libtool. Libtool claims to support some AIX and sunos targets. It supports a lot of platforms, probably more than gambit does. I don't claim to be an expert on libtool; I only started reading its info pages yesterday. They are very good. Basically you put "libtool --mode=compile" before the compiler command to create objects and it will create the subset of static and shared objects that is supported by the target, or you can specify what sort of objects you want. No other commands, such as ranlib, need to be run. Similarly there is "libtool --mode=link" for linking, "libtool --mode=execute" for execution before installation and "libtool --mode=install" for installation. Further they detail how libtool integrates with autotools. Anyway, I think I have DESTDIR support mostly done; I just need to do the linking once and set the correct rpath. Though without libtool my modifications will likely only work correctly on GNU-compatible systems. Marijn - -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML , #gentoo-{lisp,ml} on FreeNode -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkytwsACgkQp/VmCx0OL2w54ACeN0BhR6b0C/kr5p6M43qLJ8Dd QlsAoIPs/QUXqYElgHp0ErYF+hGQYWda =rHfv -----END PGP SIGNATURE-----

Re: location of libgambcgsi.so

Marc Feeley — 2008-11-30T13:37:38
On 30-Nov-08, at 7:39 AM, Marijn Schouten (hkBst) wrote: It is redundant unless your system needs it! Probably redundant on most systems, but it is a quick operations (a few seconds to relink). I forget. But it was not a single system. Wild guess: AIX and SUNOS. The makefiles predate libtool. Moreover libtool does not exist on all platforms (so using it would not be portable). I guess its existence could be tested by the configure script. How is libtool typically used for software installation? Marc

Re: Adding docs to wiki?

Marc Feeley — 2008-11-30T13:32:31
Having the documentation on the wiki or some user editable place would be useful. However, I think the documentation should be written in one "universal" markup language so that all forms of the documentation can be generated from it (.pdf, .html, .info, and "wiki" editable). Currently that markup language is texinfo. Moreover, eventually I would like the documentation for the procedures and special forms to be inside the source code and the examples in the documentation should be tested for consistency when the regression tests are run. I'm unsure how all of this can work. Is there a documentation maintenance system that supports all of this? Otherwise can one be built? Marc On 29-Nov-08, at 8:24 AM, Ali wrote:

Re: location of libgambcgsi.so

Marijn Schouten (hkBst — 2008-11-30T12:39:31
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc Feeley wrote: Hi Marc, if so, then the first compilation is redundant. Delaying linking until after install is incompatible with installing into a temporary staging area aka DESTDIR. Are you certain it is really that bad? What platform are we talking about that needs this? If you want portability shouldn't you be using libtool instead of rolling your own? Thanks, Marijn - -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML , #gentoo-{lisp,ml} on FreeNode -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkyiYMACgkQp/VmCx0OL2wKXACdENnzgOHjOX6e4437Rhu30sEh bdEAn3cxGxgwjg72OUipsqvMQImHXGKi =Jjvi -----END PGP SIGNATURE-----

Re: Termite, IO and memory leakage

Christian Jaeger — 2008-11-30T09:35:35
Hello Just to be sure: you *are* running a Termite which contains all fixes from SVN, i.e. your version *does* contain the "Fixed issues with unsafe procedures in base-exception-handler" patch? I'm asking since some people are still running into the segfault with the unsafe ##cmd-b call whose argument order did change; recent Gambit means you need the above patch. Christian.

Re: location of libgambcgsi.so

Marc Feeley — 2008-11-30T04:13:10
On 29-Nov-08, at 6:44 PM, Marijn Schouten (hkBst) wrote: On some systems, when a program is linked against a shared library, it is important to link the program when the shared library is in the final (installed) location. This way it is not necessary for the library to be in the PATH (actually LD_LIBRARY_PATH or similar) at run time. Perhaps this is not needed on many, if not most, systems. But in the interest of portability this is how it is done for all systems. Marc

Re: location of libgambcgsi.so

Marijn Schouten (hkBst — 2008-11-29T23:44:43
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marijn Schouten (hkBst) wrote: Alright, that probably wasn't the right question. I've been staring at configure.ac and mostly gsi/makefile.in a lot. The files libgambcgsi.so and gsi for exmaple seem to get built twice. Once during "make": $(LIBRARY): $(LIBRARY_OBJECTS_IN_COMPILE_ORDER) rm -f $(LIBRARY) < at >MAKE_LIBRARY< at > which on my system results in: x86_64-pc-linux-gnu-gcc -Wl,-O1 -rdynamic -shared -o libgambcgsi.so _gsilib.o _gambcgsi.o ../lib/libgambc.so -lutil -ldl -lm and once during "make install": install-post: all $(srcdirpfx)$(rootfromhere)/mkidirs $(bindir) $(INSTALL_DATA) $(srcdirpfx)_gambcgsi.c $(libdir)/_gambcgsi.c - --> < at >MAKE_LIBRARY_FOR_INSTALL< at > $(INSTALL_LIB) $(LIBRARY) $(libdir)/$(LIBRARY) < at >FIXLIB< at > $(libdir)/$(LIBRARY) #for library in $(LIBRARIES_SCM); do \ # $(INSTALL_DATA) $$library $(libdir)/$$library; \ #done < at >LINK_FOR_INSTALL< at > $(INSTALL_PROGRAM) $(EXECUTABLE) $(bindir)/$(EXECUTABLE) which results in: x86_64-pc-linux-gnu-gcc -Wl,-O1 -rdynamic -shared -o libgambcgsi.so _gsilib.o _gambcgsi.o /usr/lib/libgambc.so -lutil -ldl -lm you can see the second compilation of gsi there too (< at >LINK_FOR_INSTALL< at >). The first time is: $(EXECUTABLE): $(EXECUTABLE_OBJECTS_IN_COMPILE_ORDER) $(LINK_LIBS) < at >LINK< at > What is the point of doing all this? Marijn - -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML , #gentoo-{lisp,ml} on FreeNode -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkx0+sACgkQp/VmCx0OL2wUSQCeIid1fMjkdyOPMk5uyx8ogoQR uj4An0dRn0KHBku0OtlZbRo8zYtZECgP =PTjR -----END PGP SIGNATURE-----

Re: Adding docs to wiki?

Christian Jaeger — 2008-11-29T15:28:39
SVN isn't a distributed VCS. Also, wikis which are just using Git as centralistic storage backend (maybe as plugin) without offering access to branching don't count. You really have to write code for new workflow models to take advantage of it. Christian.

Re: Adding docs to wiki?

Sven Hartrumpf — 2008-11-29T14:37:13
_______________________________________________ Gambit-list mailing list Gambit-list< at >iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

Re: Adding docs to wiki?

Nguyen Thai Ngoc Duy — 2008-11-29T14:10:45
cairographics.org already uses a Git backed wiki: ikiwiki. But well I'd love to see a Gambit-based wiki system.

Re: Adding docs to wiki?

Christian Jaeger — 2008-11-29T14:04:13
What will be different from the current possibility to change the documentation, namely using a Gambit Git checkout and a text editor to edit doc/gambit-c.txi in texinfo markup? * it may be newbie friendlier (web browsers and wiki markup being the tools first used by new computer users nowadays); it may be questionable how much of an advantage inviting newbies is actually, though * it allows to split the docs into smaller units; but I think the existing texinfo converters can already do that, too * wikis may have a nicer default layout than the currently offered html output of the texinfo converter: but I suppose that could easily changed too, if it matters at all * it offers a more informal way of passing over thoughts, i.e. less for changing the actual documentation but for adding comments; I think this would probably be a good thing, but I wonder whether it wouldn't be a better solution to just have an annotation functionality for that; examples for such user annotated documentations: http://www.php.net/manual/en/tutorial.firstpage.php http://dev.mysql.com/doc/refman/5.1/en/apache.html * the versioning functionality in current wiki systems is much worse than something like Git; not only don't they offer distributed versioning, but also almost no tool access to work with; so merging back changes which happened on the wiki to the Gambit sources will be a manual process just as it will be a manual process to update the wiki documentation with changes happening in the Gambit sources; you should probably be willing to be the manual replacement for good tools for both of these directions. I've been thinking for some time now that it's time for someone writing a wiki with a Git backend for storage; and optional forking for updates, so each user can work with his own branch [if he wants], [either online or offline], before merging back changes to the canonical location. And if that wiki would support texinfo as markup [or something that offers lossless conversion from/to texinfo, or Gambit moving to a different markup] then it would all become much more workable. Since there are some web frameworks for Gambit out there already, why not start such a wiki implementation? That would really be wonderful, even just for working with "normal" wiki content, not especially documentation. I'd help with the Git interfacing. Christian.

Adding docs to wiki?

Ali — 2008-11-29T13:24:53
_______________________________________________ Gambit-list mailing list Gambit-list< at >iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

location of libgambcgsi.so

Marijn Schouten (hkBst — 2008-11-28T02:02:22
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, which line of configure.ac or one of the makefile.in's determines what the exact path, as given by the first line of output of the command "readelf -d /usr/bin/gsi", is at which the executable gsi searches for libgambcgsi.so in the case that gambit has been configured with --enable-shared? Thanks, Marijn - -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML , #gentoo-{lisp,ml} on FreeNode -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkvUS0ACgkQp/VmCx0OL2xLvACgsfu1/jL9knChwRm6Mm+0sDk/ f0oAoIR9xtjtgiZNiXB4BOBsRX3Reval =bk9I -----END PGP SIGNATURE-----

[ANN] Gambit-C v4.3.2 released

Logiciel Gambit — 2008-11-27T19:34:15
Gambit-C v4.3.2 is now available. Changelog: http://www.iro.umontreal.ca/~gambit/repo/.cgit.cgi/Gambit/log/ The sources and prebuilt distributions can be obtained from the Gambit web site by visiting one of the following links. sources: http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/source/gambc-v4_3_2.tgz (for typical users) http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/source/gambc-v4_3_2-devel.tgz (for developers) prebuilt: http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-macosx-G3.dmg http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-macosx-G4.dmg http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-macosx-G5.dmg http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-macosx-intel32.dmg http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-macosx-intel64.dmg http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-macosx-universal.dmg http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-windows-mingw.exe http://www.iro.umontreal.ca/~gambit/download/gambit/v4.3/prebuilt/gambc-v4_3_2-windows-visualc.exe

[PATCH] Make unclean exception handling clean again

Christian Jaeger — 2008-11-27T13:08:01
After breakfast I realize that the "cleanness" the routine is referring to was probably not the stripping of continuation frames from the sight of the user, but the calling of (release-ownership!). Now how to fix this? The approach in this patch is to run (release-ownership!) in the repl-context as did the old code, but then run the original handler in the context of the error; well this means that we will be in a repl while ownership has been released, dunno if that's a good thing. Possibly an alternative might be using |dynamic-wind| instead? I don't know what the onwership exactly implies. Signed-off-by: Christian Jaeger pflanze.mine.nu> --- Apply on top of the previous patch. As usual with "git am -3 emailfile" lib/_repl.scm | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/lib/_repl.scm b/lib/_repl.scm index fe41fb6..9765661 100644 --- a/lib/_repl.scm +++ b/lib/_repl.scm < at >< at > -2291,7 +2291,16 < at >< at > (lambda () (release-ownership!) (macro-raise exc))) - (old-handler exc))) + (continuation-capture + (lambda (cont) +(##continuation-graft + (macro-repl-context-cont repl-context) + (lambda () + (release-ownership!) + (##continuation-graft + cont + (lambda () + (old-handler exc))))))))) thunk))) (define (acquire-ownership!)

Thank you for Gambit

Mikael More — 2008-11-27T12:29:49
_______________________________________________ Gambit-list mailing list Gambit-list< at >iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

[PATCH] Make "clean exception handling" switchable,and off by default

Christian Jaeger — 2008-11-27T11:04:56
Introduces a parameter object in |current-clean-exception-handling|, which is set to #f by default. With clean exception handling switched off, exceptions happening during macro expansion trap into the repl at the point of the error. Signed-off-by: Christian Jaeger pflanze.mine.nu> --- Example: $ cat t.scm (define-macro (hello . body) (let ((v (error "an error"))) `(display (list "Hm: " ',v ',body)))) (hello "hua") > (include "t.scm") *** ERROR IN #, "t.scm"< at >2.12 -- an error 1> ;; restore the old behaviour: > (current-clean-exception-handling #t) > (include "t.scm") *** ERROR -- an error > lib/_repl.scm | 23 +++++++++++++++-------- 1 files changed, 15 insertions(+), 8 deletions(-) diff --git a/lib/_repl.scm b/lib/_repl.scm index 3dc0aac..fe41fb6 100644 --- a/lib/_repl.scm +++ b/lib/_repl.scm < at >< at > -2275,17 +2275,24 < at >< at > (##exit)) + +(define current-clean-exception-handling (make-parameter #f)) + + (define-prim (##repl-within cont write-reason) (define (with-clean-exception-handling repl-context thunk) - (##with-exception-catcher - (lambda (exc) - (##continuation-graft ;; get rid of any useless continuation frames - (macro-repl-context-cont repl-context) - (lambda () - (release-ownership!) - (macro-raise exc)))) - thunk)) + (let ((old-handler (current-exception-handler))) + (with-exception-handler + (lambda (exc) + (if (current-clean-exception-handling) + (##continuation-graft ;; get rid of any useless continuation frames + (macro-repl-context-cont repl-context) + (lambda () +(release-ownership!) +(macro-raise exc))) + (old-handler exc))) + thunk))) (define (acquire-ownership!) (##repl-channel-acquire-ownership!))