Re: [PATCH] doc: describe the -e (module) shorthand as on equal footing with (@ ...)

Arne Babenhauserheide skribis: > From 4751b9c4c85152281f0d57eda6a1c4ce50166ad4 Mon Sep 17 00:00:00 2001 > From: Arne Babenhauserheide > Date: Thu, 29 Sep 2016 17:11:26 +0200 > Subject: [PATCH] describe the -e (module) shorthand as on equal footing with > (@ ...) > > * doc/ref/guile-invoke.texi,

GNU Guile 2.0.14 released

We are pleased to announce GNU Guile release 2.0.14, the next maintenance release for the 2.0.x stable series. This release contains 18 commits by 5 people over 4 months. Guile is an implementation of the Scheme programming language. It is designed to help programmers create flexible application

Re: The status of JIT compiler of Guile

Howdy! Andy Wingo skribis: > And hello Atsuro! I don't think I have had the chance of expressing to > you how impressive your work is. Awesome stuff!!! +1! > What do you all think is the way forward for this work? Is it something > that you see being integrated eventually into Guile git? I

Re: Guile 2.1.8 on 9 March / 2.2.0 on 16 March

Hello Guilers! Andy Wingo skribis: > An update on Guile 2.2 status. As I mentioned in a previous mail, I > think the master branch is good to go. I spent some time over the last > week going over bugs; I have looked at all bugs in our database (!), > fixed a number of them (check https://debbu

Re: Guile foreign object interface

Hello! I think Mark made two kinds of comments back then: 1. There were suggestions about the API itself, nothing deep: . Andy, do you know if they’ve been addressed? 2. A general concern about “API churn” and ou

Re: Guile foreign object interface

Howdy! Andy Wingo skribis: > On Tue 07 Mar 2017 14:44, l...@gnu.org (Ludovic Courtès) writes: > >> I think Mark made two kinds of comments back then: >> >> 1. There were suggestions about the API itself, nothing deep: >> <https://lists.gnu.org/archive/

Re: Enable truncation of exception output

Hello! Andy Wingo skribis: > On Fri 03 Feb 2017 14:40, Daniel Llorens writes: > >> The patch to master (ice-9 boot-9) lets you override the (format) used >> internally by the exception printers. Then I rewrite the format string >> in user code, see below. It's a bit hacky, maybe someone has a b

Re: bug#72913: Guile 3.0.10 fails to build for powerpc-darwin (3.0.9 built earlier)

Hi Sergey, Sergey Fedorov skribis: > :info:build In language/cps/guile-vm.scm: > :info:build 89:31 2 (target-symbol-hash _) > :info:build 41:18 1 (jenkins-lookup3-hashword2 > "call-with-escape-continuation") > :info:build In ice-9/boot-9.scm: > :info:build 1676:22 0 (raise-exception

Re: [Guile-commits] GNU Guile branch, string_abstraction2, updated. fc50695e8d6a5cc0cebc3a8fcd0833ec1ff316a2

Hello! Mike Gran writes: > Setting a port's default encoding to Latin-1 doesn't work out so well in > practice. For example, ports are used as the backend of procedures like > with-input-from-file and with-output-to-string. Those procedures don't > currently take any encoding information and p

Re: [Guile-commits] GNU Guile branch, master, updated. 782a82eed13abb64393f7acad92758ae191ce509

Hey, Andy Wingo writes: >>> + uniform-array->bytevector >> >> I would not export it from `(rnrs bytevector)' given that it has nothing >> to do with RnRS. > > No, but it does have to with bytevectors... Where would you put it? Dunno, maybe not anywhere public? >> Also, I would make t

Re: Andy Wingo --> THANKS

Mark H Weaver writes: > I know I'm new here, but I'm sure we can all agree that Andy Wingo has > earned a spot in the top section of the THANKS file. And `AUTHORS' as well I guess. :-) Ludo'.

Re: guile and emacs: unexec

Hello! Ken Raeburn writes: > I've updated to recent Emacs sources and Guile 1.8.6. I've gotten it > to a point where it seems to start up fine in tty mode, reads in (and > does color highlighting of) C files and directories, does some other > basic stuff. Woowww, impressive! Looking forward t

Re: NEWS entries -- user-visible?

Hello, Andy Wingo writes: > Specifically, I am going to remove the following NEWS entries, which are > great stuff but thankfully invisible to the user: > > ** Guile now uses Gnulib as a portability aid > > ** Primitive procedures (aka. "subrs") are now stored in double cells > This

Re: NEWS entries -- user-visible?

Hello! Neil Jerram writes: > Julian Graham writes: > >>>    ** Guile now uses Gnulib as a portability aid >> >> ** Guile now uses components from Gnulib for portability to a wider >> variety of POSIX and non-POSIX systems. > > I see where you're heading with this, but for me this NEWS item stil

Re: release update

Andy Wingo writes: > One question is that I've been calling this thing 1.9.1 under the > assumption that we made a 1.9.0; but that does not seem to be the case. > Should this one be 1.9.0 or 1.9.1? I'd say 1.9.0. > guile-config and pkg-config We should deprecate the former, BTW, if this hasn't

Re: [Guile-commits] GNU Guile branch, master, updated. fa1804e94394d92b9999eaee769653ed423474b3

Hi! "Andy Wingo" writes: > +** Scheme expresssions may be commented out with #; > + > +#; comments out an entire expression. See the R6RS for more information. Is there any difference between SRFI-62 and R6RS here? If not, let's mention the former, which is older than the latter. Thanks, Ludo

Re: [Guile-commits] GNU Guile branch, master, updated. 782a82eed13abb64393f7acad92758ae191ce509

Hi, Andy Wingo writes: > On Thu 18 Jun 2009 22:28, l...@gnu.org (Ludovic Courtès) writes: > >> Andy Wingo writes: >> >>>>> + uniform-array->bytevector >>>> >>>> I would not export it from `(rnrs bytevector)' given that

Re: Again on Windows support (2)

Hi Carlo, "carlo.bramix" writes: > : In procedure dynamic-func in expression (dynamic-call > "scm_init_programs" (dynamic-link "libguile")): > : No error Can you try to change the following lines in : --8<---cut here---start->8--- SCM_INTERNAL void scm_init

Re: NEWS entries -- user-visible?

Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> I think GNU users, especially on non-GNU platforms (proprietary Unices, >> etc.), have come to know what Gnulib is, and to appreciate it >> (hopefully), which is why I thought it would make sense to me

Re: NEWS entries -- user-visible?

Neil Jerram writes: > I'm really not sure. It's an interesting idea. And I think it > touches on the part of GNU philosophy that tries not to draw a firm > line between users and developers. Do you think it's worth asking > people on gnu-prog-discuss? Yes, why not. Would you like to do this?

Re: Again on Windows support (2)

"carlo.bramix" writes: > make[3]: Entering directory `/home/Carlo/guile/module' > /usr/bin/mkdir -p `dirname system/base/pmatch.go` > ../pre-inst-guile-env ../guile-tools compile -o "system/base/pmatch.go" > "/cygdrive/c/msys/1.0/home/Carlo/guile-svn/module/system/base/pmatch.scm" BTW, this is

GNU Guile 1.9.0 released (alpha)

the `master' branch of Git have version number 1.9.x. Guile versions with an odd middle number, e.g., 1.9.*, 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 of the Guile team. pgpvmcUhcIm7Y.pgp Description: PGP signature

Re: GNU Guile 1.9.0 released (alpha)

Hi, Linas Vepstas writes: > Running r6rs-ports.test > /bin/sh: line 4: 7268 Segmentation fault ${dir}$tst > FAIL: check-guile Can you try to reproduce this? Run "ulimit -c unlimited" before (or similar) so that we can get a backtrace. Thanks in advance, Ludo'.

Re: GNU Guile 1.9.0 released (alpha)

Hello! Andy Wingo writes: > On Sat 20 Jun 2009 00:05, l...@gnu.org (Ludovic Courtès) writes: > >> We are pleased to announce GNU Guile release 1.9.0. > > Thank you for doing the release! Thank *you* for doing most of the work! >> Guile is an interpreter, compiler, and

Re: GNU Guile 1.9.0 released (alpha)

Hello, Mike Gran writes: > --- a/libguile/r6rs-ports.c > +++ b/libguile/r6rs-ports.c > @@ -210,7 +210,10 @@ static SCM > cbp_mark (SCM port) > { >/* Mark the underlying method and object vector. */ > - return SCM_PACK (SCM_STREAM (port)); > + if (SCM_PTAB_ENTRY (port) != NULL) > +re

Re: GNU Guile 1.9.0 released (alpha)

l...@gnu.org (Ludovic Courtès) writes: > Mike Gran writes: > >> --- a/libguile/r6rs-ports.c >> +++ b/libguile/r6rs-ports.c >> @@ -210,7 +210,10 @@ static SCM >> cbp_mark (SCM port) >> { >>/* Mark the underlying method and object vector.

Re: Brainfuck branch

Hey! Andy Wingo writes: > scheme@(guile-user)> ,L brainfuck > Guile Brainfuck interpreter 1.0 on Guile 1.9.0 > Copyright (C) 2001-2008 Free Software Foundation, Inc. > > Enter `,help' for help. > brainfuck@(guile-user)> ++initializes cell zero to 10 > ...

Re: 1.9.1 release on 15 July, freeze on 10 July

Andy Wingo writes: > I propose that we make the next release on 15 July, to get back onto the > on-the-15th schedule. Let's have a 5-day freeze. That means that any > feature that you want to land has to be in by two weeks from Friday -- > if it's not *ready* by 10 July, please hold off until the

Re: bytevector docs -> compound data types?

Hello, Andy Wingo writes: > Currently the bytevector docs are in the "Simple data types" section. > Would they not be a better fit in "Compound data types", along with > uniform vectors &c? See http://lists.gnu.org/archive/html/guile-devel/2009-05/msg00077.html . An argument in favor of the cu

Re: 1.9.1 release on 15 July, freeze on 10 July

Andy Wingo writes: > Grand! Ludovic, if you don't mind, perhaps we can repeat the same > division of labor as last time? Yes, please. Speaking of which, I'm not sure what to do regarding `GUILE-VERSION'. I'm tempted to leave everything as is for the whole 1.9 series because it's a development s

Re: data-crunching in guile

Hi, Andy Wingo writes: > What I'm getting at is that I think we should have VM ops for working on > vectors -- both generic vectors, and specific ops for bytevectors, and > probably an op for string-ref as well, and possibly string-set!. Then a > native code backend could be effectively implemen

Guile and GDB

Hello, "Neil Jerram" writes: > The first kind is that libguile includes the utility functions > gdb_print, gdb_eval, etc., and the variable gdb_output. These have no > purpose except for developers to use from GDB when debugging > something. For example, if you have a SCM x and

Re: Guile and GDB

Hi Neil, Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Actually, it's also meant to be used directly by GDB. Normally, GDB >> should try to display SCM values on its own (using its own copy of >> `tags.h' and the corresponding printing pr

Re: Guile and GDB

Hello, Neil Jerram writes: >> Neil Jerram writes: >> >>> Wow, that's pretty cool! So your patches are actually in GDB now, are >>> they? >> >> Yes, but as I said, they're not too useful as it stands. > > I don't really understand why you say that. They look useful to me. Because one can achi

Re: MinGW build fixes

Hello! Neil Jerram writes: > - MinGW can't export/import struct variables from/to a DLL, so wrap > the ones needed by inline.h in exported/imported pointer variables. [...] > * libguile/gc.h (scm_i_freelist_ptr, scm_i_freelist2_ptr, > scm_i_master_freelist_ptr, scm_i_master_freelist2_ptr):

Re: NEWS entries -- user-visible?

Hi! Neil Jerram writes: > "In addition to its manual, the package should have a file named > @file{NEWS} which contains a list of user-visible changes worth > mentioning. ..." > > So I'd say that use of Gnulib (in general) should not be a NEWS item. > I think HACKING would be the right place to

Re: Guile and GDB

Hello! Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Because one can achieve the same result with simple GDB macros such as >> those attached below (actually Andy put similar macros in the >> repository). > > Thanks for explaining, I understan

Reporting unused local variables

Hello, The attached patch is an attempt to add unused variable reporting to the compiler, at the GLIL->assembly step. It was quite simple to implement here, and it should work with all front-ends (Scheme, ECMAScript, etc.), which is nice. Example: --8<---cut here---start

Re: r6rs libraries, round two

Hello! Julian Graham writes: > It's a fine way of handling version-less dependencies, but I don't see > how it solves the determinism issue. Let's say my program (or code > stream or script or whatever you want to call it) uses libraries from > two different authors. Author A trusts his depend

Re: NEWS entries -- user-visible?

Hello, Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: >> (I think we don't disagree on what `NEWS' should contain, but on whether >> Gnulib qualifies as "user-visible".) > > I would certainly agree that individual portability fixes shoul

Bytevector VM ops

Hello, I'm finally looking into these new VM ops... "Andy Wingo" writes: > +#define BV_FIXABLE_INT_REF(stem, fn_stem, type, size) \ > +{ \ > + long i;

Re: Bytevector VM ops

Good morning, Andy Wingo writes: > On Tue 30 Jun 2009 00:23, l...@gnu.org (Ludovic Courtès) writes: > >> "Andy Wingo" writes: >> >>> +#define BV_FIXA

Re: load_extension tests broken

Hello, Neil Jerram writes: > Andy Wingo writes: > >> On Fri 22 Aug 2008 11:56, l...@gnu.org (Ludovic Courtès) writes: >> >>> Just to make sure, I also ran `pre-inst-guile', typed >>> "(use-modules (ice-9 i18n))" and attached GDB to it: it

Re: array handles and non-local exits

Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Not quite. If get/release are left as is (i.e., they do not establish a >> dynwind context), I would write something along the lines of: >> >> You must take care to always unreserve an array af

Re: complex number reader bug?

Hello, Neil Jerram writes: > Firstly, now that 1.9.0 has been released, I'm not sure it makes sense > for 1.9.x NEWS to refer to `Changes in 1.8.x' for x >= 7. IMO, when 2.0 is released, we really want to show changes since the 1.8.x series, i.e., essentially broad changes, rather than changes

Re: array handles and non-local exits

Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: >> Maybe 1.8.7 is approaching now? > > Yes, that would be good. It might just be worth fixing the jmp_buf > definition problem before that (which I should get to in the next week > or so) - but on the other

Re: Enormous benchmark speedup

Hi! Juhani Viheräkoski writes: > With recent changes in guile vm there are lots on improvements on the > Gambit benchmarks. Improvements compared to what? > In the worst case some test run 10% slower Slower than what? > but there are huge wins in testcases involving vectors offsetting > thi

Re: truth of %nil

Hi, Mark H Weaver writes: > I've been considering writing a python compiler for guile. For python > (and others) there are several values considered to be false, such as > 0 and various empty collections, and so a different approach will have > to be taken to this problem. [...] > So how abou

Re: Reporting unused local variables

Hello, l...@gnu.org (Ludovic Courtès) writes: > The attached patch is an attempt to add unused variable reporting to the > compiler, at the GLIL->assembly step. It was quite simple to implement > here, and it should work with all front-ends (Scheme, ECMAScript, etc.), >

Re: array handles and non-local exits

Hello, Andy Wingo writes: > I'm hacking on this code right now, and have come to think that > scm_array_handle_release is superfluous. It shouldn't protect against > concurrent modification of the data, as that should be done with > user-implemented mutexen. It obviously doesn't do anything now

GNU Guile 1.8.7 released

ince the 1.3.* series. Please report bugs through the Savannah bug tracker: https://savannah.gnu.org/bugs/?group=guile Alternatively, bug reports can be sent 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. pgpFl0qZBuMLg.pgp Description: PGP signature

Re: array handles and non-local exits

Hello, Andy Wingo writes: > Good question. I suppose you have this case in mind: > > (define s0 (string "foo")) > (define s1 (substring/shared s0 0)) > (define s2 (substring/shared s1 0)) > (par-for-each (lambda (s) (string-set! s 0 #\b)) > (list s0 s1 s2)) Yes. OTO

Re: truth of %nil

Hi, Neil Jerram writes: > There are ways of writing compile time asserts; see > http://www.jaggersoft.com/pubs/CVu11_3.html for some. I don't know > how portable these all are, but at work we use the case label one, and > that seems to be good on common platforms. Gnulib's `verify' module prov

Re: array handles and non-local exits

Hello, Andy Wingo writes: > On Mon 06 Jul 2009 21:30, l...@gnu.org (Ludovic Courtès) writes: [...] >> Yes. OTOH, the doc doesn't say that concurrent array accesses are safe, >> so array accesses are supposed to be synchronized at the application >> level, using mu

Re: array handles and non-local exits

Hey, Andy Wingo writes: [...] > You can't just write functions that return values, you have to contort > code to store temporaries and then release and then return. You have > to write paired statements. If you call a user function, you really > should set up a dynwind, which conses, and contor

Re: Build failure on master

Hi Mike, Mike Gran writes: > ERROR: In procedure make_objcode_by_mmap: > ERROR: bad header on object file: "GOOF-0.5" Make sure to remove all `.go' files from your source tree and from the cache (either `~/.guile-ccache' or `~/.cache/guile/ccache'). Then hopefully you'll be able to compile Gui

Re: Build failure on master

Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Hi Mike, >> >> Mike Gran writes: >> >>> ERROR: In procedure make_objcode_by_mmap: >>> ERROR: bad header on object file: "GOOF-0.5" >> >> Make sure to remo

Re: Build failure on master

Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Hi Mike, >> >> Mike Gran writes: >> >>> ERROR: In procedure make_objcode_by_mmap: >>> ERROR: bad header on object file: "GOOF-0.5" >> >> Make sure to remo

Re: Current git unitialized vars warnings.

Hi, writes: > The new vector vm code gives me quite a few "possible use uninitialized" > warnings. > > On debian Etch: > > $ gcc --version > gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) > > Patch attached (I hope). I'm not seeing it myself (GCC 4.3.3, x86_64-linux-gnu), but I commit

Re: Build failure on master

Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: [...] >> Eventually, maybe it could handle this gracefully. For instance, if >> said object file is from the cache, then it could just recompile and >> overwrite it with a new object file. > > Yes, this is

Re: Emacs Lisp, macros

Hi Daniel! Daniel Kraft writes: > yesterday and today I implemented lambda expressions and > defvar/defconst/defun for elisp Great news! > as well as found a (hopefully good) solution to automatically create > fluids not yet present on reference. Is each Elisp variable mapped to a fluid? Ev

Re: updated NEWS, release tomorrow

Hey! Andy Wingo writes: > I've updated the NEWS as best I could for happenings between 1.9.0 and > 1.9.1. They're notable to us, but fortunately many of the changes since > the last release are just changes to 1.9 code that won't be visible to a > 1.8 user. Anyway, check the NEWS, or if you're t

Re: updated NEWS, release tomorrow

Hey! Andy Wingo writes: > All summer? I'm in France frequently. Perhaps one day we should meet up! I'm frequently there, too, so I'd be happy to join in! Perhaps we should set up a GNU Guile Hackers Meeting (G²HM) by the time 2.0 is released? Ludo'.

GNU Guile 1.9.1 released (alpha)

umbers 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. pgp2unTF1KbBh.pgp Description: PGP signature

Re: array handles and non-local exits

Hi Neil, Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Andy Wingo writes: [...] >>> Array_handle_release is a bad idea. >> >> Fair enough. > > FWIW, I agree (I think with both of you) that `we might need it in > future' is

GNU Guile Hackers Meeting?

Hello! Neil Jerram writes: >> Perhaps we should set up a GNU Guile Hackers Meeting (G²HM) by the time >> 2.0 is released? > > If it works for everyone, why not? To make things more concrete, how about August 22--23? It works for Andy and me. We could meet someplace in the Pyrénées---how nice

GNU Guile Hackers Meeting?

Hello! Neil Jerram writes: >> Perhaps we should set up a GNU Guile Hackers Meeting (G²HM) by the time >> 2.0 is released? > > If it works for everyone, why not? To make things more concrete, how about August 22--23? It works for Andy and me. We could meet someplace in the Pyrénées---how nice

Re: GNU Guile Hackers Meeting?

Hi Mike! Mike Gran writes: > I can't make it.  I live in Los Angeles, and I have tickets for the > Warped Tour punk festival on the 23rd. Eh eh. It's a bit Western Europe centric, indeed, but I think at least Julian and you are on the American continent so perhaps you could set up a meeting

Re: Segfault with do (Re: [CM] funny scheme code (fwd))

Hello Kjetil, "Kjetil S. Matheussen" writes: > Guile 1.8.0 segfaults as well. > > Here's the code ready for pasting: > > (let ((j (lambda () 0)) > (k 0)) > (do ((i (j) (j)) > (l (lambda () 1) (lambda () (+ i 1 > ((= i 3) k) > (set! k (+ k i > > Sorry fo

Re: review/merge request: wip-array-refactor

Hello! Andy Wingo writes: > I've finished up my refactor of Guile's arrays. To my eye it's much > nicer now. Hey, great! Several general remarks: * Since I'm conservative and lazy, I'd have happily let this code rest in peace. ;-) In particular, last time I checked[*], we had poor

Re: Reporting unused local variables

¡Hola! Andy Wingo writes: > OK, here's another idea. Why don't we keep this as a separate pass -- > enabled if you pass a compilation option. That way it can be more > functional, and you can keep approximate source information. By "pass", you mean a new "language" in the tower? As in `lookup-

Re: GNU Guile Hackers Meeting?

Neil Jerram writes: > I'm afraid a whole weekend is not possible for me, as it's family > time. Is during the following week (24th-28th) any good for you? Yes, on the 24th. (I'd probably take this opportunity to walk with my relatives in the mountains the day(s) before.) > You'd be very welco

Merging libguile-i18n with libguile

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

Re: Quasisyntax broken?

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

Re: Quasisyntax broken?

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

Re: Reporting unused local variables

Hello Guilers! Here's a third attempt. This time, it's done as a separate pass at the tree-il level *and* in a purely functional way. I owe a great debt to a famous Scheme hacker whose paper /Applications of fold to XML transformation/ was a invaluable source of inspiration [0]. Thanks! :-) I

Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-1-17-g77332b2

Hello! "Michael Gran" writes: > The branch, master has been updated >via 77332b21a01fac906ae4707426e00f01e62c0415 (commit) > from e5dc27b86d0eaa470f92cdaa9f4ed2a961338c49 (commit) Oops, I hadn't realized this was in `master'. Was it intended? (I don't remember seeing a discuss

Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-1-18-g904a78f

"Michael Gran" writes: > commit 904a78f11d2d11a58d5df365a44c4fbbd4c96df3 > Author: Michael Gran > Date: Wed Jul 29 06:38:32 2009 -0700 > > Add 32-bit characters > > This adds the 32-bit standalone characters. Strings are still > 8-bit. Characters larger than 8-bit can only b

Re: Reporting unused local variables

you try it with the Elisp front-end and report back? I'm planning to add warnings for possibly unbound variables, and global bindings unused in the current module and not exported (and eventually anything Guile-Lint supported). Thanks, Ludo'. commit 4b856371b3e85cd82f6d637f72bc610d0158b5d

`(language elisp spec)' broken in `master'

Hello! `(language elisp spec)' is broken in `master', but I guess that's because Daniel's elisp branch is where things happen. Anyway, just in case, here are the issues: --- a/module/language/elisp/spec.scm +++ b/module/language/elisp/spec.scm @@ -1,6 +1,6 @@ -;;; Guile Emac Lisp +;;; Guile Emac

Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-1-17-g77332b2

Hi Mike, Mike Gran writes: > On Fri, 2009-07-31 at 00:57 +0200, Ludovic Courtès wrote: > Hello! >> >> "Michael Gran" writes: >> >> > The branch, master has been updated >> >via 77332b21a01fa

Re: `(language elisp spec)' broken in `master'

Hi Daniel, Daniel Kraft writes: > you're right, I think all I did ever do on elisp is on the branch -- > module/language/elisp and spec.scm were there already, I don't know > who created them an when... OK. > So I think this is worth fixing in order to allow building master, but > otherwise i

Re: guile performance - Ackermann function: way slower than emacs, slower still if compiled

Hello! Andy Wingo writes: > Perhaps the deal is that 1+ is not being inlined. It seems to be calling > out to the 1+ procedure, which is a primitive, actually making it a > bit slower. I'll see what I can do. Currently, invoking subrs conses, which is Bad(TM). Code that keeps invoking `1+' and

Re: Elisp performance

Hi! Andy Wingo writes: > Dynamic-wind, on the other hand, does pose a problem. The problem is > that dynamic-wind is a primitive -- to call it, the VM saves its > registers, conses together its arguments, and passes them to the > evaluator. The evaluator destructures the consed list, eventually

Re: review/merge request: wip-array-refactor

Hi Andy! Andy Wingo writes: > The second model is when you already have a wide deployed base. You can > make additions to your API and ABI, and deprecated old API or ABI, but > you can't remove old API or change the ABI. Incompatible breaks are > painful, and the switching-over time is somewhere

Unicode strings and symbols

Hi Mike! Glad to see Unicode has landed! :-) Here's a quick review of the big patch. "Michael Gran" writes: > Add Unicode strings and symbols > > This adds full Unicode strings as a datatype, and it adds some > minimal functionality. The terminal and port encoding is assumed

Guile 2.x and `pkg-config'

Hello, A recent thread on `guile-user' [0] raises an important concern: what should we do with `guile-1.8.pc' when 2.x is out? How about shipping `guile-1.8.pc' for compatibility, along with `guile.pc' (which would then become the Right One), both with "Version: 2.0"? Thoughts? Ludo'. [0] http

Using a linker version script

Hello, The patch at [0] makes it so that a linker version script (info "(ld) VERSION") is used for `libguile' on platforms that support it (GNU and Solaris). Comments welcome! Ludo'. [0] http://git.savannah.gnu.org/cgit/guile.git/commit/?id=9af080f7206dccffb91409529fff74e6554f2385

Re: Unicode strings and symbols

Hey, Mike Gran writes: [...] >> > +SCM_API void scm_charprint (scm_t_uint32 c, SCM port); >> >> This ought to be internal, no? > > Could be. A couple of the types are given their own print functions: > scm_intprint and an scm_uintprint. Most types don't have their own > print functions. Are

Re: i guess we're frozen & stuff

Mike Gran writes: > Hmmm.  I should have been watching the clock.  I've left master in > an odd state w.r.t. strings and chars.  The storage is available for > non-8-bit strings and chars, but, nothing can be done with them. I don't think it's a serious issue. Just a small comment: --8<---

Re: i guess we're frozen & stuff

Ken Raeburn writes: > ../../guile-readline/../libguile/strings.h:26:21: error: uniconv.h: No > such file or directory > > Neither the path specified for libgmp nor the path specified for > libunistring at configure time is included here. Ag, that's what I feared with the inclusion of libunis

Re: i guess we're frozen & stuff

Hi, Ken Raeburn writes: > It appears that the word size and endianness is also encoded into the > header. Is this a good idea, when people can share home directories > across machines of different architectures, and even run mixed-size > binaries on a single system (or mixed-architecture, in so

Re: i guess we're frozen & stuff

Greg Troxel writes: > FAIL: bytevectors.test: 2.9 Operations on Strings: string->utf8 [latin-1] > FAIL: bytevectors.test: 2.9 Operations on Strings: utf8->string [latin-1] Does libunistring's "make check" pass on this platform? > FAIL: i18n.test: locale objects: make-locale with unknown locale

Re: i guess we're frozen & stuff

Mike Gran writes: > All of srfi-13.c isn't ready to operate on non-8-bit strings. string=? > calls MY_VALIDATE_SUBSTRING_SPEC_COPY, which calls scm_i_string_chars. > scm_i_string_chars either returns a pointer to the Latin-1 strings or > errors with the error you saw. OK, thanks for the explana

Re: i guess we're frozen & stuff

Greg Troxel writes: > Does libunistring's "make check" pass on this platform? > > should have tried that. testlocale.c fails on line 38 with: Can you report it upstream? > So it seems that NULL is expanding to (void *) 0, and "sizeof (void *) > 0" is not legit. AFAIK sizeof is specified to

i18n issues on NetBSD

Greg Troxel writes: > scheme@(guile-user)> (make-locale LC_ALL "does-not-exist") > # And `(setlocale LC_ALL "does-not-exist")'? It looks like setlocale(3) doesn't behave as specified by POSIX (http://www.opengroup.org/onlinepubs/9699919799/functions/setlocale.html). > scheme@(guile-user)> (map

Re: i guess we're frozen & stuff

Greg Troxel writes: > #define NULL (void *)0 This is under-parenthesized! Two actions to be taken: 1. Report a bug to your favorite libc maintainers. ;-) 2. Ask libunistring folks at http://savannah.gnu.org/projects/libunistring/ to replace "sizeof NULL" by "sizeof (NULL)" in `

Re: i guess we're frozen & stuff

Ken Raeburn writes: > Just checking: I assume we don't care about binary compatibility > between 1.9.x unstable releases? Hence changing function signatures > and structure contents, and deleting symbols, while not changing the > library's major version number, is okay? Yes. Ludo'.

Re: i guess we're frozen & stuff

Mike Gran writes: >> From: Juhani Viheräkoski moonsh...@kapsi.fi [...] >> strings.c: In function ‘scm_string_append’: >> strings.c:1300: error: ‘data’ may be used uninitialized in this function >> make[3]: *** [libguile_la-strings.lo] Error 1 [...] > This one's okay, I think.  The allocation

Re: i guess we're frozen & stuff

Ken Raeburn writes: > However, they're testing for a POSIX 2008 requirement that C99 and > POSIX 2004 implementations need not meet, namely that NULL be of type > "void *" instead of any null pointer constant (e.g., "0"). I think > requiring POSIX 2008 support for Guile and anything that builds

<    5   6   7   8   9   10   11   12   13   14   >