Hello Guilers of the Guild!
Andy Wingo wi...@pobox.com writes:
So! My new proposal is guild.
[...]
But that doesn't mention the real advantage of guild, which is how you
feel when you type it or tell it to someone: that you pertain to a
secret society of wizards! Who wouldn't want to
Hello!
Andy Wingo wi...@pobox.com writes:
On Mon 28 Mar 2011 22:40, l...@gnu.org (Ludovic Courtès) writes:
1. Disable pthread redirects and instead register threads explicitly
(in ‘scm_with_guile’).
Why is this only applicable to 2.1 ?
I was thinking it’d break the ABI, but maybe
Hello,
Mike Gran spk...@yahoo.com writes:
Partially related to all of this is that there are compilation issues
on Cygwin. Cygwin runs bdw-gc 7.1. That version of bdw-gc does have
headers that mention pthreads, but, doesn't really support cygwin's emulation
of them. So I tried configure
Hi,
Tristan Colgate tcolg...@gmail.com writes:
Think I found a problem with void returns for pointer-procedure,
the following gives a segfault...
A SIGABRT actually.
(use-modules (system foreign))
(define (myproc)
(display hello)(newline))
((pointer-procedure
void
Hello!
Andy Wingo wi...@pobox.com writes:
Sure. Sorry for the precipitous action. That said, this bug has been
open since September: https://savannah.gnu.org/bugs/?32436
Oh indeed, I hadn’t realized there’s a connection; still...
Do you have any thoughts on that bug,
The problem is
Hello,
Andy Wingo wi...@pobox.com writes:
On Mon 28 Mar 2011 21:22, l...@gnu.org (Ludovic Courtès) writes:
The problem is that libgc ends up being initialized behind our back upon
the first libgc-redirected ‘pthread_create’ call.
Indeed.
Hans Boehm suggested [0] two solutions:
1
Hello!
Neil Jerram n...@ossau.uklinux.net writes:
l...@gnu.org (Ludovic Courtès) writes:
Hello,
A few more thoughts...
Andy Wingo wi...@pobox.com writes:
On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
bdw-gc 6.8 compatibility
Hello,
Andreas Rottmann a.rottm...@gmx.at writes:
l...@gnu.org (Ludovic Courtès) writes:
[...]
Besides it’s still unclear (to me) what the future of Wak and similar
projects is. I hope that it will take off, but I haven’t forgotten
Snow, ScmPkg, etc. either.
Well, there's a (IMHO
Hello!
Andy Wingo wi...@pobox.com writes:
On Mon 07 Mar 2011 22:14, l...@gnu.org (Ludovic Courtès) writes:
Thoughts?
Thanks for dealing with Guile-lib's bugs! I went ahead and pushed a
0.2.0 release.
Excellent! (I see 8942bd0cf6192526af5490a7c26ff1cef0fe3916 makes it
clear that (sxml
Hello!
Andreas Rottmann a.rottm...@gmx.at writes:
l...@gnu.org (Ludovic Courtès) writes:
Hi!
Andreas Rottmann a.rottm...@gmx.at writes:
+SCM_DEFINE (scm_fixnum_p, fixnum?, 1, 0, 0,
+(SCM x),
+Return @code{#t} if @var{x} is a fixnum, @code{#f}
otherwise
Hello!
Andy Wingo wi...@pobox.com writes:
commit 5f0d2951a0a5179038bee55fe9af688f94738075
Author: Andy Wingo wi...@pobox.com
Date: Thu Mar 24 20:34:31 2011 +0100
bdw-gc 6.8 compatibility (hopefully)
* configure.ac (HAVE_GC_STACK_BASE): New check.
*
Hello,
Andy Wingo wi...@pobox.com writes:
I think we made a mistake in exposing bdw-gc.h to libguile.h users.
gc.h is quite scrupulous to not include it, but smob.h, inline.h
(sometimes), and pthread-threads.h pull it in.
libguile/bdw-gc.h is intentionally pulled because our public headers
Hi,
Andy Wingo wi...@pobox.com writes:
On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
bdw-gc 6.8 compatibility (hopefully)
Aarrrgh. The intent has always been to support 7.x only (bdw-gc.h has
compatibility stuff for historical
Hi,
Mike Gran spk...@yahoo.com writes:
The Guile web site links to a doc on lonelycactus.com, which I'm going
to repurpose at somepoint in the future. The doc is way obsolete, so it
should probably be de-linked.
Done,
Ludo’.
Hi Andreas!
Andreas Rottmann a.rottm...@gmx.at writes:
l...@gnu.org (Ludovic Courtès) writes:
[...]
Could you send a patch to update the manual?
I have started working on this,
Great!
but I'm notorious (at least to myself) for starving
documentation-related work with interesting coding
Hello,
Andreas Rottmann a.rottm...@gmx.at writes:
l...@gnu.org (Ludovic Courtès) writes:
[...]
I think it would make sense to include ‘fmt’ in core Guile only if the
API is reasonably stable and there are infrequent upstream releases, so
we don’t quickly end up shipping an old incompatible
Hi Andreas,
I’m all for your suggestion.
Andreas Rottmann a.rottm...@gmx.at writes:
+ (define-syntax define-fxop*
+(syntax-rules ()
+ ((_ name op)
+ (define name
+ (case-lambda
+((x y)
+ (assert-fixnum x y)
+ (op x y))
+(args
+
Hi!
Andreas Rottmann a.rottm...@gmx.at writes:
+SCM_DEFINE (scm_fixnum_p, fixnum?, 1, 0, 0,
+(SCM x),
+Return @code{#t} if @var{x} is a fixnum, @code{#f} otherwise.)
+#define FUNC_NAME s_scm_fixnum_p
+{
+ return scm_from_bool (SCM_I_INUMP (x));
+}
+#undef
Hello!
Andy Wingo wi...@pobox.com writes:
On Sun 20 Mar 2011 22:31, l...@gnu.org (Ludovic Courtès) writes:
[...]
Thus ‘%target-type’ would be inappropriate IMO because the target could
be chosen at run-time and it could be anything.
‘guile-tools compile --target=TRIPLET’ would be fine
Hello!
Andy Wingo wi...@pobox.com writes:
It's true that a simple command-line argument and fluid could work, but
the situation will get more complicated, so we will need some part of
Guile to define the host and target triplets. That's the questions I
was really asking: where in Guile to
Hi!
Andy Wingo wi...@pobox.com writes:
On Sun 20 Mar 2011 14:50, l...@gnu.org (Ludovic Courtès) writes:
[...]
However, I don’t think defining ‘%target-type’ would make sense
since:
1. Of the GNU triplet, only the $target_arch matters for bytecode;
2. You can really choose at run
Hello Unicode fellows! :-)
Mark H Weaver m...@netris.org writes:
Andy Wingo wi...@pobox.com writes:
Ludovic, Andy and I discussed this on IRC, and came to the conclusion
that UTF-8 should be the encoding assumed by functions such as
scm_c_define, scm_c_define_gsubr,
Hi Mark,
Mark H Weaver m...@netris.org writes:
l...@gnu.org (Ludovic Courtès) writes:
We keep wide (UTF-32) stringbufs as-is, but we change narrow stringbufs
to UTF-8, along with a flag that indicates whether it is known to be
ASCII-only.
The whole point of the narrow/wide distinction
Hi!
Thanks for the brave threading debugging. :-)
Andy Wingo wi...@pobox.com writes:
No, the issue is elsewhere, that the thread-exit handlers were not being
called
I just tried with 60582b7c2a495957012f9a20cd8691dc6307a850 and
‘on_thread_exit’ /is/ called after something like
Hey!
Andy Wingo wi...@pobox.com writes:
it has a pleasant subject-verb-object when you say it: Guido, compile
my-file.scm.
Is the pun[*] intended? :-)
FWIW I’m happy with the verbose name and I fear the joke wouldn’t be to
everyone’s taste. I’d also be happy with a shorter name, though.
Hello Andy!
Andy Wingo wi...@pobox.com writes:
On Sun 06 Mar 2011 23:12, l...@gnu.org (Ludovic Courtès) writes:
Neil Jerram n...@ossau.uklinux.net writes:
In principle, how should Guile 2.0 be cross-compiled? I'm thinking
mostly of the part of the build that compiles all the installed
Hello!
The problem is that modules are resolved at compile-time, in addition to
run-time, so there just can’t be circular dependencies.
Besides, I think it’s generally a problem from an engineering viewpoint
when cycles are introduced.
So my feeling is that Guile should be able to detect cycles
Hi Mark,
Mark H Weaver m...@netris.org writes:
I have a compromise proposal, which could be implemented for 2.0.x:
We keep wide (UTF-32) stringbufs as-is, but we change narrow stringbufs
to UTF-8, along with a flag that indicates whether it is known to be
ASCII-only.
The whole point of the
Hi!
Mark H Weaver m...@netris.org writes:
(string-upcase Straße) = STRAßE (should be STRASSE)
(string-downcase ΧΑΟΣΣ)= χαοσσ (should be χαoσς)
(string-downcase ΧΑΟΣ Σ) = χαοσ σ (should be χαoς σ)
(string-ci=? Straße Strasse) = #f(should be #t)
Hello Mark,
Mark H Weaver m...@netris.org writes:
Mike Gran spk...@yahoo.com writes:
The reason I am still arguing this point is because I have looked
seriously at what I would need to do to (A) fix our i18n problems and
(B) make the code efficient. I very much want to fix these things,
Hi,
Mike Gran spk...@yahoo.com writes:
From:Ludovic Courtès l...@gnu.org
I know of two categories of bugs. One has to do with case conversions
and case-insensitive comparisons, which must be done on entire strings
but are currently done for each character. Here are some examples:
Hello,
Andreas Rottmann a.rottm...@gmx.at writes:
Not that I have any say in that, but IMHO, it would be preferable to
keep external libraries maintained separatly from the Guile core;
however in this case, including it in the core might be justified by its
proposed use in the JIT compiler.
Hi,
[Cc: Jim Bender.]
I can reproduce the problem:
--8---cut here---start-8---
scheme@(guile-user) (define sxml '(*TOP* (*PI* xml version=\1.0\
encoding=\UTF-8\) (note
(to Tove)
(from Jani)
(heading Reminder)
(body Don't forget me
Hello,
A bit of explanation for commit
ca33b501a93f8de389c1e3e1bc987f63b6912029...
Try this:
--8---cut here---start-8---
(use-modules (srfi srfi-1)
(srfi srfi-9))
(define-record-type foo
(make-foo x)
foo?
(x foo-x))
(define register!
Hi Mark,
Mark H Weaver m...@netris.org writes:
Unfortunately, the alternatives are not pleasant. We have a bunch of
bugs in our string handling functions. Currently, our case-insensitive
string comparisons and case conversions are not correct for several
languages including German,
Hello Andreas,
Thanks, I’ve applied all these.
Could you send a patch to update the manual?
Thanks,
Ludo’.
Hello!
Mark H Weaver m...@netris.org writes:
I claim that any reasonable code which currently uses string-ref and
string-set! could be more cleanly written using string ports or
string-{fold,unfold}{,-right}.
I agree, and we should encourage this. However...
I find Cowan’s proposal for
Hi,
Bruce Korb bk...@gnu.org writes:
So, this should go under:
#if GUILE_VERSION 20 // anything after 2.0, e.g. 2.0.1 ??
Rather use AC_CHECK_FUNC.
Thanks,
Ludo’.
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
l...@gnu.org (Ludovic Courtès) writes:
Hi,
Andy Wingo wi...@pobox.com writes:
On Sun 06 Mar 2011 23:26, l...@gnu.org (Ludovic Courtès) writes:
Andreas Rottmann a.rottm...@gmx.at writes:
The expansion of `define-inlinable
Hello,
Noah Lavine noah.b.lav...@gmail.com writes:
We talked about having a Scheme-based language that could compile to
both plain C and JIT, but decided that would make the VM too
complicated,
Maybe I forgot to feed that thread, but I think it might be easier to
have a high-level
Hi,
Andy Wingo wi...@pobox.com writes:
On Sun 06 Mar 2011 23:26, l...@gnu.org (Ludovic Courtès) writes:
Andreas Rottmann a.rottm...@gmx.at writes:
The expansion of `define-inlinable' contained an expression, which made
SRFI-9's `define-record-type' fail in non-toplevel contexts (definition
Hi Dale,
dsm...@roadrunner.com writes:
[...]
/home/dsmith/src/guile-lib/doc//guile-library.texi:2204: Cross reference to
nonexistent node `SRFI-1 Fold and Map' (perhaps incorrect sectioning?).
makeinfo: Removing output file `guile-library.info' due to errors; use
--force to preserve.
Hello!
Actually, a fun project would be to implement Nix storage model, its
build primitive (‘derivation’), and assorted tools (garbage collector,
etc.) in Guile Scheme. It doesn’t seem unrealistic, though it’s perhaps
another project; OTOH you mentioned rollback so it’s not completely
Hi!
Noah Lavine noah.b.lav...@gmail.com writes:
I've been toying with the idea of an AOT compiler for Guile, and I
think that would make a good summer project.
Really? I thought you were toying with JIT. :-)
I think you'd want to compile from Tree-IL to GCC's GIMPLE format (the
Hi!
Noah Lavine noah.b.lav...@gmail.com writes:
Yes, it's been a while since we talked about that :-). I still want to
do it, though. The current status as I see it is that I have a
prototype JIT that works, and a plausible way to integrate it into
Guile's VM. What needs to happen now is to
Hi!
Andy Wingo wi...@pobox.com writes:
SCM scm_public_lookup (SCM module_name, SCM sym);
SCM scm_private_lookup (SCM module_name, SCM sym);
Look up a variable bound to SYM in the module named MODULE_NAME. If
the module does not exist or the symbol is unbound, signal an
Hi,
I’ve pushed a variant of this patch.
Thanks,
Ludo’.
Hi Neil,
Neil Jerram n...@ossau.uklinux.net writes:
In principle, how should Guile 2.0 be cross-compiled? I'm thinking
mostly of the part of the build that compiles all the installed modules.
Guile 2.0 can only be cross-compiled when the endianness and word size
of the host and target match
Hi Alex,
Alex Shinn alexsh...@gmail.com writes:
2011/3/7 Ludovic Courtès l...@gnu.org:
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
The expansion of `define-inlinable' contained an expression, which made
SRFI-9's `define-record-type' fail in non-toplevel contexts (definition
Hi,
Andy Wingo wi...@pobox.com writes:
On Mon 21 Feb 2011 07:02, Mike Gran spk...@yahoo.com writes:
I find that the backtrace output in the REPL is too constrained
my verbose code. The attached patch would let one set the
width of the backtrace and locals meta-commands.
What do you
Hi Hans,
Hans Aberg haber...@telia.com writes:
On 3 Mar 2011, at 00:03, Ludovic Courtès wrote:
scheme@(guile-user) (define libm (dynamic-link
/usr/lib/libm.dylib)) ERROR: In procedure dynamic-link: file:
/usr/lib/libm.dylib, message: file not found
You should omit the extension, which
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
Another related issue that has come up in IRC is versioning: If I
understand correctly, it is currently impossible to specify the version
of the shared object to be used (as one cannot even pass a full filename
to `dynamic-link'). This
Hi,
Hans Aberg haber...@telia.com writes:
On 3 Mar 2011, at 11:40, Ludovic Courtès wrote:
The crux is that on older MacOS X versions ‘.dylib’ are shared
libraries (not dlopenable), whereas ‘.so’ are “bundles”
(dlopenable). That’s why lt_dlopenext (which is what
‘dynamic-link’ uses) doesn’t
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
I wonder how this generally should be handled -- I think the most
appropriate way would be to commit any changes that can go into the
stable release into stable-2.0 (only), and then, at convenient times
(perhaps always before committing
Hi,
Andreas Rottmann a.rottm...@gmx.at writes:
l...@gnu.org (Ludovic Courtès) writes:
Andreas Rottmann a.rottm...@gmx.at writes:
Another related issue that has come up in IRC is versioning: If I
understand correctly, it is currently impossible to specify the version
of the shared object
Hi!
dsm...@roadrunner.com writes:
The other day, aidalgol and I were chatting on irc about the new ffi.
The question came up about how to define and access nested structures.
I couldn't tell from reading the manual if it can be done.
There are ‘parse-c-struct’ and ‘make-c-struct’ examples in
Hi,
Michael Ellis michael.f.el...@gmail.com writes:
scheme@(guile-user) (define libm (dynamic-link /usr/lib/libm.dylib))
ERROR: In procedure dynamic-link: file: /usr/lib/libm.dylib,
message: file not found
You should omit the extension, which will be automatically inferred by
Guile (actually
Hi,
Hans Aberg haber...@telia.com writes:
On 2 Mar 2011, at 21:44, Ludovic Courtès wrote:
scheme@(guile-user) (define libm (dynamic-link /usr/lib/libm.dylib))
ERROR: In procedure dynamic-link: file: /usr/lib/libm.dylib,
message: file not found
You should omit the extension, which
Hi David,
David Fang f...@csl.cornell.edu writes:
/* The type of subrs, i.e., Scheme procedures implemented in C. Empty
function declarators are used internally for pointers to functions of
any arity. However, these are equivalent to `(void)' in C++, are
obsolescent as of C99, and
Hi,
Mike Gran spk...@yahoo.com writes:
Also, is the libunistring dependency still necessary,
Yes, e.g., in scm_from_stringn. Besides we may eventually provide
bindings for other parts of libunistring, like ‘unicode_character_name’,
etc.
Thanks,
Ludo’.
Hi,
Andy Wingo wi...@pobox.com writes:
But you have to, I think. If that module that contained the above
define-syntactic-accessor expansion exports foo, then in another
module you have:
(define bar (lambda () (foo)))
which expands to
(define bar (lambda () val-234123))
Val needs
Hello!
We don't do “Fix letrec (reloaded)”, so ‘letrec*’ (and thus internal
defines) are compiled sub-optimally:
--8---cut here---start-8---
scheme@(guile-user) ,c (letrec* ((x 2)(y 3)) y)
Disassembly of #objcode 1ea7a28:
0(assert-nargs-ee/locals 16)
Hi!
BTW I added cross-compilation jobs to Hydra (the ‘xbuild_*’ things):
http://hydra.nixos.org/jobset/gnu/guile-2-0/
The cross-MinGW one needs some love, but at least the cross-GNU one
works fine without special hacks.
Thanks,
Ludo’.
Hi Mark,
Mark H Weaver m...@netris.org writes:
I recently noticed that scm_i_big2dbl contains some crufty and
inefficient compatibility code to work around unspecified rounding
behavior of mpz_get_d in GMP prior to version 4.2. GMP 4.2 was released
in March 2006 and has been in Debian since
Hi,
Andreas Rottmann a.rottm...@gmx.at writes:
That's not true for '$(...)', see SUSv3, Section 2.6.3.
Solaris 5.10 /bin/sh:
--8---cut here---start-8---
echo $(echo foo)
syntax error: `(' unexpected
--8---cut
Hi Jan,
Jan Nieuwenhuizen janneke-l...@xs4all.nl writes:
ERROR: In procedure module-lookup:
ERROR: Unbound variable: for-each
It’s very likely another problem with the ‘merge-generics’ strategy.
Would you like to debug further, e.g., by adding ‘pk’s in boot-9.scm in
‘merge-generics’?
Hi,
Mike Gran spk...@yahoo.com writes:
From:Mark H Weaver m...@netris.org
Mark wrote:
It seems to me that *width* should not be a global variable, but rather
a per-repl setting. It probably belongs in the options field of the
repl record, no? See repl-default-options in
Hi,
Bruce Korb bk...@gnu.org writes:
By replacing scm_listofnull with ag_scm_listofnull and initializing
it:
SCM ag_scm_listofnull = scm_list_1 (SCM_EOL);
In Guile 1.9.3, you have to scm_gc_protect_object this value
(info (guile) Garbage Collection Functions).
and it sounds like
Hello,
Andy Wingo wi...@pobox.com writes:
On Mon 21 Feb 2011 21:50, l...@gnu.org (Ludovic Courtès) writes:
--- a/libguile/ports.c
+++ b/libguile/ports.c
@@ -661,6 +661,19 @@ scm_i_remove_port (SCM port)
scm_port_non_buffer (p);
p-putback_buf = NULL;
p-putback_buf_size = 0
Hi!
Andy Wingo wi...@pobox.com writes:
On Tue 22 Feb 2011 12:36, l...@gnu.org (Ludovic Courtès) writes:
+
+ if (p-input_cd != (iconv_t) -1)
+{
+ iconv_close (p-input_cd);
+ p-input_cd = (iconv_t) -1;
+}
+
+ if (p-output_cd != (iconv_t) -1
Hi Guilers!
I agree with your suggestions.
I think ‘stable-2.0’ should only get changes that preserve the C ABI and
Scheme interface.
Additions of new public functions/procedures or modules are generally
welcome though they should discussed on a case-by-case basis IMO.
Thanks,
Ludo’.
Hi!
Andy Wingo wi...@pobox.com writes:
fix a couple leaks in ports.c. thanks valgrind!
* libguile/ports.c (scm_i_remove_port): Fix a case in which ports
explictly closed via close-port would leak their iconv_t data.
(scm_set_port_encoding_x):
Hi!
Here’s a proposal for a condensed NEWS for the announcement:
Highlights of changes in 2.0.0 (since the 1.8.x release series):
* New compiler infrastructure and VM
Guile 2.0 compiles Scheme code to bytecode, which is then interpreted
by the VM. This gives a noticeable performance
versions. Even middle numbers indicate stable versions.
This has been the case since the 1.3.* series.
Please report bugs to `bug-gu...@gnu.org'. We also welcome reports of
successful builds, which can be sent to the same email address.
Ludovic Courtès, on behalf of the Guile team
Hi Mark,
Mark H Weaver m...@netris.org writes:
I apologize for asking you again so soon, but could you possibly import
log1p from gnulib?
[...]
If it's easy to import a couple more modules while you're at it, then
round and isfinite would also be useful.
Done, except for ‘isfinite’, which
Hi Mark,
This patch series seems to break compilation on i686-linux-gnu:
http://hydra.nixos.org/build/913079
The relevant part of the log is:
Running numbers.test
FAIL: numbers.test: Number-theoretic division: truncate/: mixed types: (130.0
10/7)
FAIL: numbers.test: Number-theoretic
Hello!
There’s now a ‘stable-2.0’ branch!
We’re releasing in less than 24 hours so normally nothing will be pushed
there. :-)
There’s an additional jobset on Hydra for this branch:
http://hydra.nixos.org/jobset/gnu/guile-2-0
Normally you should soon be able to grab a tarball from there and
Hi Mark,
Mark H Weaver m...@netris.org writes:
The first patch here is a trivial comment fix for numbers.test.
The second patch fixes some serious problems in the logarithm functions
when applied to large integers, large or small fractions, or fractions
with large numerators and
Hi,
Andy Wingo wi...@pobox.com writes:
On Sun 13 Feb 2011 10:58, Neil Jerram n...@ossau.uklinux.net writes:
No. But that might be because the libgc on that machine - Debian
1:7.1-3 - is too old. What is the latest recommendation for libgc
version? README says at least version 7.0, but I
Hi!
Noah Lavine noah.b.lav...@gmail.com writes:
The attached patch does it. I almost hate to commit it because it's
such a hack, but this is from my last Guile session:
scheme@(guile-user) 'foo
$2 = foo
scheme@(guile-user) 'foo ; hi there!
$3 = foo
scheme@(guile-user) ; why, hello!
Hi!
Andy Wingo wi...@pobox.com writes:
Cool. Generally Ludovic has been handling the gnulib imports. Perhaps
he can add trunc to the module list whenever he does the next import.
Done.
Ludo’.
Hi,
Jan Nieuwenhuizen janneke-l...@xs4all.nl writes:
gnulib-tool --import --dir=. --lib=libgnu --source-base=lib --m4-base=m4
--doc-base=doc --tests-base=tests --aux-dir=build-aux --libtool
--macro-prefix=gl --no-vc-files alignof alloca-opt announce-gen autobuild
byteswap
Hi,
Andy Wingo wi...@pobox.com writes:
Are these lines in load.c right?
/* The file has no encoding declared. We'll presume Latin-1. */
scm_i_set_port_encoding_x (port, NULL);
I thought we were defaulting to UTF-8 now.
Yes, ‘compile-file’ defaults to UTF-8, so the above line
Hi Julian,
Julian Graham jool...@gmail.com writes:
Do you think you’ll be able to work on it by Tuesday? :-)
I was planning to devote some time to it this weekend. (Is it okay if
the changes go up before the release?)
Great. It’s even preferable if the changes are made before the
Andy Wingo wi...@pobox.com writes:
On Fri 11 Feb 2011 17:01, l...@gnu.org (Ludovic Courtès) writes:
I guess that's what we need to do with the libtools that are out
there.
The libtool invocations you mean?
No, the libltdls. I was thinking about getting some other API into
ltdl, instead
Hi Andy,
Andy Wingo wi...@pobox.com writes:
On Tue 23 Nov 2010 21:56, l...@gnu.org (Ludovic Courtès) writes:
In 1.8, to run the test suite of libguile-foo from its build tree, I
typically had a ‘pre-inst-guile’ like this:
exec @abs_top_builddir@/libtool --mode=execute
Hi Julian!
These all sound like great ideas to me! You normally have access to the
web page repository, so feel free to commit your changes there and just
send a note so we can check what’s up there.
IMO the parts discussing features or technical merits should be really
concise. It could even
Hello,
Andy Wingo wi...@pobox.com writes:
On Tue 08 Feb 2011 00:13, Göran Weinholt go...@weinholt.se writes:
I'm wondering if it wouldn't make more sense to have these reader
options by associated with each port.
Probably, yes. Would be a larger refactor, though.
I think ports and reader
Hello!
Andy Wingo wi...@pobox.com writes:
On Thu 03 Feb 2011 10:14, Mark H Weaver m...@netris.org writes:
This patch implements the ideas outlined in my response to Mike Gran's
recent post entitled Effects of updated number fixes on parsing.
Applied, and thanks again for the high quality
Hello!
And thanks for the patch stream and quick fixes! :-)
Mark H Weaver m...@netris.org writes:
Ah, I was using a non-portable extension of isinf(x) to determine the
sign of the infinity. This patch should fix it.
We use Gnulib’s ‘isinf’ module. It could be that it’s buggy, or it
could
Hello,
Neil Jerram n...@ossau.uklinux.net writes:
l...@gnu.org (Ludovic Courtès) writes:
Guile 2.0 is a breakthrough in Guile's history. First and foremost, it
is based on a compiler and a virtual machine. The compiler compiles
Scheme code to bytecode, applying well-known optimizations
.*, are unstable
development versions. Even middle numbers indicate stable versions.
This has been the case since the 1.3.* series.
Please report bugs to `bug-gu...@gnu.org'. We also welcome reports of
successful builds, which can be sent to the same email address.
Ludovic Courtès, on behalf
Hi Jan,
Jan Nieuwenhuizen janneke-l...@xs4all.nl writes:
Ludovic Courtès schreef op za 29-01-2011 om 22:34 [+0100]:
[...]
Hmm could it be that there was a typo? Here running ‘git-version-gen’
outside of a Git tree works fine:
$ guile/build-aux/git-version-gen .tarball-version s/foo
Hello!
Jan Nieuwenhuizen janneke-l...@xs4all.nl writes:
Ludovic Courtès schreef op za 29-01-2011 om 22:39 [+0100]:
[...]
I’m not sure about this patch. My feeling is that it would take more
than this to allow Guile to be truly relocatable, e.g., all of
$GUILE_LOAD_PATH
Hi!
Jan Nieuwenhuizen jann...@gnu.org writes:
Ludovic Courtès schreef op ma 31-01-2011 om 22:00 [+0100]:
Hi,
Your patch lacks this RPATH magic, though.
Yes, we have that in our GUB cross build system. Possibly this
is a thing/feature request for libtool.
Perhaps it should check
Hi!
Andy Wingo wi...@pobox.com writes:
On Sat 29 Jan 2011 23:54, Hans Aberg haber...@telia.com writes:
On 29 Jan 2011, at 21:53, Ludovic Courtès wrote:
I think there should be a mailing list for people who implement
Schemes, to sort of coordinate our non-standard features. ...
I think
Hi Noah,
I think several Schemes already have a dynamic FFI with a C parser.
Bigloo has one (info (bigloo) Automatic extern clauses generation),
and it’s GPL’d code, which we could reuse. Larceny has something too.
Thanks,
Ludo’.
Hi,
I think several Schemes already have a dynamic FFI with a C parser.
Bigloo has one (info (bigloo) Automatic extern clauses generation),
and it’s GPL’d code, which we could reuse. Larceny has something too.
Oh, great. Can Guile reuse GPL'd code, though, since it is LGPL?
We could have
Hello!
l...@gnu.org (Ludovic Courtès) writes:
(define-syntax define-wrapped-pointer-type
(lambda (stx)
(syntax-case stx ()
((_ pred wrap unwrap print) ;; hygiene
(with-syntax ((type-name (datum-syntax #'pred (gensym)))
(%wrap (datum-syntax #'wrap
Hello!
While using (system foreign) in a couple of projects I found myself
doing quite a bit of pointer arithmetic in Scheme:
--8---cut here---start-8---
(define (foreign-array-list array-pointer element-count)
(let ((array (pointer-bytevector array-pointer
1101 - 1200 of 2428 matches
Mail list logo
