At least I could easily put raw logs available to my webpage, I run the
benchmarks by hand anyway. Then I could try to polish my hacked benchmark
suite and send it upstream. There were some bugs introduced by my porting
efforts, I *think* I've fixed them all now :) If someone wants to try it it'
Hi,
szgyg writes:
> 5. Parameters in libguile_i18n...@libguile_i18n_major@_la_LDFLAGS is
> wrong (libguile/Makefile.am line 135). Please copy from other .so's
> LD_FLAGS, as the others build fine.
I've seen this report before, but FWIW, I've been thinking about merging
libguile-i18n into libgui
Hi Andreas,
Andreas Rottmann writes:
> I think I filed one for Guile several years ago, and think you assume
> rightly;
Yes, you're on file.
> I guess that might be a problem; OTOH it would be (IMHO) kinda dumb to
> have to ignore/rewrite all the perfectly (L)GPL-compatible BSD- and
> MIT-lic
Hi,
On Sat 25 Jul 2009 23:30, Andreas Rottmann writes:
> Andy Wingo writes:
>
>> On Fri 24 Jul 2009 00:35, Andreas Rottmann writes:
>>
>>> Andy Wingo writes:
>>>
On Fri 03 Jul 2009 02:04, Andreas Rottmann writes:
> Playing around with Guile's now-in-core syntax-case support (us
Hi,
Andy Wingo writes:
> Hm. I have no idea what this means for Guile. It seems we need either a
> disclaimer or an assignment.
My understanding is that it's OK if we have bits of code not copyright
FSF, if there's a good reason to do so (and there is one, here).
After some reading, I see this
Hi-
I wonder if I could get someone to check out what I've done with wide
strings and the VM on the string_abstraction2 branch with commit
efb042...
That code is quite confusing, and I may have made a mess of it. And, I
wasn't sure about alignment.
I daresay that this Unicode string stuff is no
