Howdy!
Andy Wingo writes:
> It would be nice to add it in 2.0.x, as it's a compatible change.
OK, sounds good! I guess you’ll have to add the explanation of why the
name’s so great to the manual. :-)
> But, there's no need for it to hold back a 2.0.1 release; there's a
> lot of NEWS to write
On Thu 31 Mar 2011 05:51, Mike Gran writes:
> dynamic-pointer relies on lt_dlerror for its error message, and that
> procedure can return the unhelpful string "No Error" when lt_dlsym
> fails to find a symbol. You might fix it like I did in the following
> patch.
Cool. Applied something simila
Hi Diogo,
On Mon 28 Mar 2011 06:51, "Diogo F. S. Ramos" writes:
> I've been following some discussions about GSoC here and in the IRC and
> I would like to say that I would love to work with you in this winter
> ;).
Cool! As you see, we can be a bit asynchronous in our communications
;-)
> I
Hi Juhani,
Sorry for the delay in the response!
On Wed 02 Mar 2011 09:22, "Juhani Viheräkoski" writes:
> $ ./test-script
> ;;; note: source file /home/misty/moonshine/yarg/scripts/./race
> ;;; newer than compiled
> /home/misty/.cache/guile/ccache/2.0-LE-4-2.0/home/misty/moonshine/yarg/scr
On Thu 31 Mar 2011 00:52, Detlev Zundel writes:
> | scheme@(guile-user)> (sqlite-open "mydb" SQLITE_OPEN_READONLY)
> | ;;; :2:0: warning: possibly unbound variable `SQLITE_OPEN_READONLY'
> | :1:0: In procedure #:2:0
> ()>:
> | :1:0: In procedure module-lookup: Unbound variable:
> SQLITE_OPEN_RE
Noah Lavine writes:
>> Not since the e-mail. I'm still waiting for feedback.
>
> I will tell you what I think, then, but keep in mind that many people
> on this list know a lot more than I do.
I really appreciate it.
> The first idea is something I think Guile people are very interested
> in, a
Hi Andy,
> On Thu 31 Mar 2011 00:52, Detlev Zundel writes:
>
>> | scheme@(guile-user)> (sqlite-open "mydb" SQLITE_OPEN_READONLY)
>> | ;;; :2:0: warning: possibly unbound variable `SQLITE_OPEN_READONLY'
>> | :1:0: In procedure #> input>:2:0 ()>:
>> | :1:0: In procedure module-lookup: Unbound varia
Hello,
Andy Wingo writes:
> Any change to Guile's internal character encoding should not start from
> the premise that string-ref is obsolete or unimportant, especially
> considering that there is no other standard "string pointer" mechanism.
+1
There are idioms like:
(let ((start (string-i
Hello!
Andy Wingo writes:
> Interesting. It seems that the string->pointer code is doing the wrong thing:
It works as advertised. :-)
-- Scheme Procedure: string->pointer string
Return a foreign pointer to a nul-terminated copy of STRING in the
current locale encoding. The C stri
>> I have my own ideas, like the Introspection branch that I forked from
>> zeenix, but I am not sure this is of the best interest for guile right
>> now.
>
> What do you want to do in this area? There is important work to do with
> introspection, but we would need to see your ideas and your code.
Hello,
Mike Gran writes:
> + const char *lt_err = lt_dlerror ();
> + if (lt_err == (const char *) NULL || strncmp (lt_err, "No Error",
> strlen ("No Error")))
> + {
> + char *msg;
> + int ret;
> + ret = asprintf (&msg, "symbol \"%s\" not found", symb);
> +
Hi :)
On Thu 31 Mar 2011 16:28, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo writes:
>
>> It seems that the string->pointer code is doing the wrong thing:
>
> It works as advertised. :-)
Sorry, I didn't mean to accuse that function, as I didn't even use it!
(define (string->utf8-poin
On Thu 31 Mar 2011 16:32, l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Mike Gran writes:
>
>> + const char *lt_err = lt_dlerror ();
>> + if (lt_err == (const char *) NULL || strncmp (lt_err, "No Error",
>> strlen ("No Error")))
>> +{
>> + char *msg;
>> + int ret;
>
l...@gnu.org (Ludovic Courtès) writes:
> Hi Peter,
>
> Peter Brett writes:
>
>> It would certainly make my life as a downstream application maintainer
>> much, much easier if all Guile API functions that accept a C string
>> argument expected UTF-8.
>
> Out of curiosity, what kind of C libraries
Hi Andy,
>> Indeed, there's no null-termination on this string. I guess we need to
>> copy into a bytevector that is longer and provide a NUL byte. Want to
>> patch that one too?
The attached patches work for me.
As a followup I'd really like to put a few statments into tests below
test/. Can
nalaginrut writes:
> I think guile on embedded device would be interesting since it has VM
> now.
Also since it has the FFI - which means being able to access lots of
libraries, without needing to prepare and cross-compile glue code.
> What kernel version your freerunner running?
2.6.34
Rega
Hi,
Peter Brett writes:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> My impression is that GLib & co. are well-equipped to deal with UTF-8
>> whereas other C libraries and programs would rather work with locale
>> encoding or ‘wchar_t’ using the standard C APIs.
>>
>
> Yep, lots of GLib.
Hello Neil,
Neil Jerram writes:
> I think I've successfully cross-compiled Guile (stable-2.0, e309f3bf9e)
> for my Freerunner phone. However, when I run it, it just keeps
> allocating memory until the OOM killer kills it:
How much RAM does it have? What is Guile doing when it gets killed? Is
On Thu 24 Mar 2011 02:25, Neil Jerram writes:
> I noticed that the filename properties in installed .go files always
> begin with "module/". Is this correct and, if not, does it matter?
>
> (For example, and-let-star.go has several occurrences of
> module/ice-9/and-let-star.scm where I'd expect
l...@gnu.org (Ludovic Courtès) writes:
> Hello Neil,
>
> Neil Jerram writes:
>
>> I think I've successfully cross-compiled Guile (stable-2.0, e309f3bf9e)
>> for my Freerunner phone. However, when I run it, it just keeps
>> allocating memory until the OOM killer kills it:
>
> How much RAM does it
Hello again,
I was about to do this, and then I discovered that it wouldn't work,
because there are a few special case PEGs that don't make sense as
macros. Specifically, in the context of a PEG, we interpret strings as
matching themselves, and those can't be made into macros.
So I went ahead and
Andy Wingo writes:
> It does matter, yes: that suffix is used for looking for a file within
> the load path, and obviously having module/ on the beginning isn't going
> to work. Good catch. You'll have to rebuild everything to get the
> right paths residualized.
>
> Pushed a fix to git.
Great,
Hello,
Just tried guile-sqlite3 - after applying the 2 patches of Detlev - and
succeeded with
sqlite-open, sqlite-prepare, sqlite-column-names [and sqlite-close]
but
scheme@(guile-user)> (sqlite-step stmt)
ERROR: In procedure pointer->bytevector:
ERROR: In proc
23 matches
Mail list logo
