gmane.lisp.scheme.gambit

Re: Adding docs to wiki?

Derek Peschel — 2008-12-02T08:49:46

Or going in a slightly different direction, what namespace should the pages be in? (Does the Gambit wiki's MediaWiki installation support namespaces?) I'll come clean... I have ulterior motives for asking the question. I use the "All pages" special page a lot, partly because it gives a one-screen overview of the wiki, partly because I have been maintaining a "Release notes" page which nothing links to. Having "All pages" suddenly grow to contain the documentation would make it much less convenient. Do you mean a naming convention for Wiki pages or the organization of the contents into pages? About a naming convention, if the documentation gets its own namespace, there shouldn't be any problem just using the Texinfo node names -- perhaps with a prefix like Section_ -- as the Wiki page names. As metadata rather than nodes, the table of contents and indices should not get any prefix though. About organizing the contents, is anything irretrievably wrong with the Texinfo organization? Specifically, usin

Re: Adding docs to wiki?

Marc Feeley — 2008-12-02T06:04:59

On 1-Dec-08, at 11:26 PM, Jonathan Arkell wrote: That's a very good point! So what I will do is settle on a formatting convention that will allow the official an unofficial parts of the documentation to be distinguished. A ... section can appear in both parts, and that should be the norm so that it is easy to move stuff from the unofficial to the official section. In other words the page will have this form ...documentation from, or suggested for inclusion in, the Gambit manual == Feedback == ...general comments, questions, bug warnings, usage tricks, annotations, and stuff to be considered for inclusion in the official part I have written a script to export the Gambit manual Texinfo sections to wiki pages, using the wiki page title to indicate what this page refers to in the manual. It shouldn't be too hard to write a script to "merge" the official part of the wiki documentation pages w

Re: Adding docs to wiki?

Jonathan Arkell — 2008-12-02T04:26:12

On 1-Dec-08, at 11:46 AM, Marc Feeley wrote: I like Special_form and Procedure_ prefixes. You might need some other prefixes as well. If you categorize all the documentation pages, you can automagickally have indexes and tables of contents built up with mediawiki. Why not Documentation_of_debugging, and Documentation_of_I/O? Again, the General Index and Concept Indexes should be handled via categories. I am not sure I understand this question. Why not handle them as wiki links? Yes. I can even try and take a stab at this if you like. I'm an okay designer, and rock solid web developer. I guess that depends on how easy it is to copy back. Something occurred to me however. Most user-level comments, questions, and additions to the documentation would probably live outside of the texinfo section--by virtue of being harder to understand then normal wiki content, whereas the texinfo sections might be reserved for documentation that would actually make it into the Gambit manual.

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:

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 tha

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. An

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

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:

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