When guile 2.0 is used to write scripts, one have to manually do a
setlocale at the beginning of the script to enable non-asciiI
character support (why not by default?).
My question is that the command line arguments seems to be parsed
before any code in the script is executed (including the setlo
On Mon, Nov 7, 2011 at 6:59 AM, David Pirotte wrote:
> You must also set port encoding, see manual section 6.14.1 for details:
>
> (set-port-encoding! (current-output-port) "utf-8")
>
Thanks for responding.
But after a setlocale, utf-8 output is already fine. The problem is
argument pars
argument list for `pointer->procedure' and generates
compound ffi types. But I don't know the right data structure to give
when actually calling the foreign function.
For example, what should I do for the following function?
typedef struct {
int dat[2];
} foo_t;
int func ( foo_t arg
ibtool
mentioned that not all loaders are able to act upon this `advice'.
--
Cong Gu
guile-2.0.5-dl-global.patch
Description: Binary data
On Sun, Jun 3, 2012 at 11:15 PM, Thien-Thi Nguyen wrote:
> () cong gu
> () Sun, 3 Jun 2012 17:04:29 -0500
>
> I found libtool offers a way to make a shared library globally
> available. So I wrote a patch that provides `dynamic-link-global'.
> A call lik
/%3a41.sls' instead of guile's way like
'srfi/srfi-41.sls'
scheme@(guile-user)> (use-modules (srfi srfi-41))
While compiling expression:
ERROR: no code for module (srfi srfi-41)
How to make them work?
--
Cong Gu
