This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I've found a LGPLed library called 'libretto' which implements some container data types like linked lists, dynamic strings/arrays, binary search trees,... in ANSI C. Quoting the introduction from the info file: ------------------------------------------------------------------------ The `GNU C Library Reference Manual' says The C language provides no built-in facilities for performing such common operations as input/output, memory management, string manipulation, and the like. Instead, these facilities are defined in a standard library, which you compile and then link with your programs. The contents of the `standard' library are defined by the ANSI and ISO C committees for general C environments, with additions by groups such as the Open Group for Unix and by the POSIX committee for Unix-like operating systems. However, some of the most commonly-desired functions and data structures are not provided by these standards, or if they are, the required complexity of the implementation is insufficient for a number of applications. This is where Libretto(1) comes in. -------------------------------------------------------------------------- Anyone have a rough idea if it would be potentially dangerous to use libguile and libretto together, by for example wrapping scheme lists into libretto lists? For a bloody newbie it sounds very tempting to use Lisp wrappers communicate with a portable implementation of lists in C, but when considering that even different Lisp dialects have communication with each other (as the guile<->elsip discussion showed), it could be more likely that someone with the experience of Stallman went through the roof when seeing such a messy approach. Klaus Schilling