Re: [PATCH] Bring `bitwise-copy-bit' behavior back in line with R6RS.

Whoops! You're right, of course. Sorry for the confusion. (I'd never read the errata - lots of neat stuff in there.) On Sep 18, 2017 2:30 AM, "Mark H Weaver" <m...@netris.org> wrote: > Mark H Weaver <m...@netris.org> writes: > > > Julian Graham <jool...

[PATCH] Bring `bitwise-copy-bit' behavior back in line with R6RS.

#node_sec_11.2 From 7a207740ffc344c7cd70411bba6c16beaea10818 Mon Sep 17 00:00:00 2001 From: Julian Graham <jool...@undecidable.net> Date: Sat, 16 Sep 2017 20:09:32 -0400 Subject: [PATCH] Bring `bitwise-copy-bit' behavior back in line with R6RS. A regression in 93da406f33 had this function copying the

Re: [PATCH] ECMAscript: Bind type names to constructor functions in the global env.

On Mon, Jan 9, 2017 at 4:20 PM, Andy Wingo wrote: > I am happy to include patches like this one. > > Yet -- *program-wrappers*, what is that about? I don't even remember > any more. I guess it's for setting a property on a function instance, > even if the function is a normal

Re: [PATCH] ECMAscript: Bind type names to constructor functions in the global env.

Hey Andy, If you're looking at patches, would you look this over and merge it if you like it? Doesn't have to go into 2.1.6 per se, but it would be cool to have it on master. On Sat, Nov 19, 2016 at 10:44 AM, Julian Graham <jool...@gmail.com> wrote: > Howdy! > > Find attached a p

[PATCH] ECMAscript: Bind type names to constructor functions in the global env.

2001 From: Julian Graham <jool...@undecidable.net> Date: Sat, 19 Nov 2016 10:28:50 -0500 Subject: [PATCH] ECMAscript: Bind type names to constructor functions in the global env. Per ECMA-262: "The Object constructor is ... the initial value of the Object property of the global ob

Re: [PATCH] Fix tree-il code generation for ECMAscript `new' expression.

So, uh... can one of the maintainers apply my patch? (Andy / Ludo / Mark?) On Tue, Sep 20, 2016 at 9:55 PM, Wilfred Hughes wrote: > Excellent :) > > I'm afraid I can't help you further, but it's great to see the > ecmascript frontend get some attention. The lack of ASI is

Re: [PATCH] Fix tree-il code generation for ECMAscript `new' expression.

Hi Wilfred, Yep! The FSF should have my assignment on file. On Tue, Sep 20, 2016 at 12:32 AM, Wilfred Hughes <m...@wilfred.me.uk> wrote: > Looks good to me (even tests)! Have you assigned copyright papers for Guile? > > On 13 September 2016 at 08:42, Julian Graham <jool..

[PATCH] Fix tree-il code generation for ECMAscript `new' expression.

b50c05 Mon Sep 17 00:00:00 2001 From: Julian Graham <jool...@undecidable.net> Date: Tue, 13 Sep 2016 08:39:43 -0400 Subject: [PATCH] Fix tree-il code generation for ECMAscript `new' expression. The compiler was producing `((toplevel foo))' instead of `(toplevel foo)'. Changed to use `call'

Possible infinite loop during compilation in 2.2

Hey Guilers, I was experimenting with building one of my projects using Guile 2.2 and found that some files just don't seem to want to finish compiling, and peg my CPU at 100% -- seems like they might be getting stuck in a loop. (Other files compile just fine.) As per some conversations with

Re: Possible infinite loop during compilation in 2.2

On Fri, Apr 18, 2014 at 3:20 PM, Andy Wingo wi...@pobox.com wrote: Interestingly this seems to happen at macro-expansion time. Did you C-c your file early, or was this after letting it run for a while? I think it was compiling for about a minute or two, which was much longer than it took to

Re: Possible infinite loop during compilation in 2.2

On Fri, Apr 18, 2014 at 3:21 PM, Julian Graham jool...@gmail.com wrote: I think it was compiling for about a minute or two, which was much longer than it took to compile everything else. I'll let it go for a good 30 minutes and send another trace. Okay, this is interesting: The stack trace

Re: Possible infinite loop during compilation in 2.2

Hey Mark, On Fri, Apr 18, 2014 at 5:43 PM, Mark H Weaver m...@netris.org wrote: Does Guile 2.0.11 or current stable-2.0 compile it correctly? I tested with a 2.0.11 built from source as well as with the stock Ubuntu 13.10 guile-2.0 package (which is 2.0.9, I think) and they both compiled it

scm_t_subr warnings

Hey Guilers, Andy and Ludo and I were discussing this on IRC and it was suggested that we move the question to the mailing list. I'm trying to compile some code -- using `gcc -pedantic' -- that invokes `scm_c_make_gsubr', and I'm getting the following warning: warning: ISO C forbids passing

srfi 64 for guile

Hi Guilers! I've got a cleaned-up version Per Bothner's SRFI 64 (A Scheme API for test suites) reference implementation that works with Guile 2.0.x sitting on my hard drive. Anyone interested in me committing it? I could add some documentation and unit tests (via Guile's own test suite API, I

[PATCH] Fix warning about extra semicolon in guile-snarf output

of a function The attached patch fixes that issue by removing a semicolon from the expansion of `SCM_STATIC_SUBR_OBJVECT'. Anyone mind if I apply it? Regards, Julian From 7cd2bf271d2063cdc3bd2827f7dc5fd9e928b446 Mon Sep 17 00:00:00 2001 From: Julian Graham julian@navigator.(none) Date: Sun, 18 Sep 2011

Re: ideas for the web site

Hey Ludovic, Great.  It’s even preferable if the changes are made before the release. :-) Alright, I think I've made the changes I described in my email. I wasn't able to commit them, though (Permission denied (publickey)) -- are you sure I've got the appropriate permissions? Using the git

Re: ideas for the web site

Hi Ludovic, 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. Yes, that was going to be my next question. :) Do you think you’ll be able to work on

Re: two oh, two oh, two oh

Hello! We could still use someone to do this -- to review the web site to see if it actually expresses the message that we want to express, and to do some PR.  I think Guile 2.0 is a good story, but the press basically needs to be spoon-fed, I think...  Anyone want to take this one?  I seem

libgc and valgrind

Hi Guilers, I wanted to report some success with using Valgrind to debug memory issues in Guile HEAD. In case you weren't aware, none of the current public releases of libgc play well with valgrind, leading to segmentation faults in the call chain originating from `scm_init_guile'. No Itisnt

Re: [PATCH] Performance improvement for R6RS records

. Regards, Julian From 8714a2a0e5713a57e292cd03f2ef91be167c6ef6 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sun, 10 Oct 2010 01:35:26 -0400 Subject: [PATCH] Improve performance of R6RS records implementation Reimplement record-type descriptors as vtables

Re: [PATCH] Performance improvement for R6RS records

Hi Andy, Do you still need some help here? I can try to work up some code to make an example. Um, yes? If you've got the time. (Sorry for the way-late reply -- I've been distracted with apartment hunting / moving.) Thanks, Julian

Re: [PATCH] Performance improvement for R6RS records

Hey Andy, Is it possible to keep the current flat record layout, and change this check to be:  (define (record-internal? obj)    (and (struct? obj)         (eq? (struct-vtable (struct-vtable obj))              record-type-vtable))) What kind of performance do you get there? I'm

[PATCH] Performance improvement for R6RS records

for SDOM (which makes extensive use of records), indicates a speedup of around 40%. Any questions? Would someone care to review before I push? Regards, Julian From be1b360fdcfa6c96ea9b0c64a7a19c05fa1650a5 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sat, 18 Sep

Re: Possible Memory Leak with stream-for-each

Hey Ludovic, On Thu, Sep 2, 2010 at 8:49 AM, Ludovic Courtès l...@gnu.org wrote: I believe this patch fixes the problem:  http://git.sv.gnu.org/cgit/guile.git/commit/?id=f57fdf07d6374028f35bcb1ee748a94022deda6d Basically ‘force’ was leaking memory because it uses ‘lock-mutex’, which was

Re: r6rs library documentation

Hi Ludovic! There’s no ‘fold’ in R6RS-lib; it’s called ‘fold-left’. Fixed -- see commit 5b379729bb5f5d06ceb02c4e96ccc62cf61f9c62. Should be “Guile’s core library (@pxref{List Modification}).” Fixed. How about this instead: �...@code{div} is an alias for Guile’s @code{quotient} and

Re: r6rs library documentation

Sounds great to me, though Brian Neil can always come in to correct me :) Done! See commit ea28e981342fd1d381e489e57cddde97eb390442. In addition to the main .texi payload, I adjusted the formatting on some of your initial paragraphs and removed the descriptions of the base and composite

Re: r6rs library documentation

Hey Andy, I think that Neil would probably have the most useful feedback, as I think he has the most global view of the manual. I am inclined to think that the level of detail is appropriate, though I imagine that Neil and Brian are cringing at the weight of the extra pages on the press ;-)

Re: r6rs library documentation

Hi all, Works for me.  I'll get started on these soon. Status update: I'm still working on the standard libraries documentation -- I'd say I'm about 70% done. I should have a draft to email out in the next week or so. Regards, Julian

Re: heads up: rename from (rnrs bytevector) to (rnrs bytevectors)

Hey Andy, Somehow we had the name of (rnrs bytevectors) wrong -- it was (rnrs bytevector). I've renamed it in git, which should make it into the 1.9.11 prerelease tonight. Sorry for the confusion! While you're looking at that, what do you want to do about the version of that module (and of

Re: r6rs incompatibilities

Hey Andy, We could make this more general, as the r7 committees are wont to do: if #! is followed by whitespace or /, then read as a block comment; otherwise read one token. In our case, we would read #!foo as #:foo. I don't think this change would affect anyone. What do you think? Note

Re: r6rs incompatibilities

inelegant) patch that adds support for the `#!r6rs' lexeme in the default reader. (What do people think about this? Is there a better way to do it?) Regards, Julian From f1af40142b47232e726cbe9f7bdc35d5fbf45602 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sun, 23

Re: r6rs incompatibilities

Hi Mike, What happens with this patch if the file only contains the four characters #!r6 followed by EOF?  Does it behave appropriately after calling scm_ungetc on EOF?  (I guess that would make it an unterminated hash bang comment.) If the fifth character is EOF instead of 'r', control is

Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-10-135-g7119448

Hi Ludo, This is a non-free document (ACM...) so I think we should not refer to it.  Perhaps instead this could read along the lines of:  ... a technique called @dfn{implicit phasing} (first described by  Abdulaziz Ghuloum and R. Kent Dybvig) ... Thoughts? Eep! My mistake. I'd found a

Re: r6rs incompatibilities

Hey Andy,  * The R6RS specifies many situations in which a conforming   implementation must signal a specific error. Guile doesn't really   care about that too much -- if a correct R6RS program would not hit   that error, we don't bother checking for it. In a lot of these cases, that's

Re: Merging R6RS libraries?

Hi all, Thanks to Andy's heroic work on the expander over the past week or so, I've just been able to merge `wip-r6rs-libraries' into `master' and push it! As you'll notice from running `make check', there are still a few issues to be addressed -- specifically, the implementation of `div' and

Re: r6rs library documentation

Hi Ludovic, My initial feeling is that there are two documentation sections to be created: A description of Guile's implementation of the R6RS `library' and `import' forms; and some notes on the bits of the R6RS Standard Libraries that Guile provides, along with pointers to more formal

Re: TODO for 2.0

Hi Andy, I'll add this to my list, then. Is there no smaller test case than compiling the entire wrapper module? Does this problem occur with smaller libraries as well? I would love to have a simple test case that I can run on master. I'll spelunk on your branch, though, if that's

Re: TODO for 2.0

Hi Andy, Please feel free to reply with your own lists. Please reply only with things that you feel must be dealt with before 2.0, by somebody, or things that you personally plan to work on (blocker or not). Unless R6RS-lib is something that can be merged in a subsequent 2.0.x stable

Re: (r6rs io ports)

Hi Mike and Ludo, Works for me.  Some questions that will have to be answered. Is there a C API for raising R6RS error conditions? No, not yet.  Actually, Julian’s work on R6RS libraries isn’t merged yet. FWIW, the way this works right now on the wip-r6rs-libraries branch is that R6RS

Re: Merging R6RS libraries?

Hi Ludo, I've got some status updates: As I said, there aren't that many libraries left to do.  Off the top of my head, the still-missing ones are (rnrs eval), (rnrs arithmetic fixnums), (rnrs arithmetic flonums), and the composite library, (rnrs rnrs).  I also want to move the library form

Re: Hierarchical name space

Hi Andy and Ludo, I'm still inclined to think that the module namespace hierarchy (and it is a hierarchy) should not impinge on the environment of an evaluation. But, not something we can change right now. This is actually causing me some difficulty -- I'm implementing the R6RS composite

Re: Merging R6RS libraries?

Hi Ludovic, Looking at messages on guile-commits, I’m really amazed by the amount of work that Julian has been doing on the R6RS front.  Now that all this code is here, I don’t see any reason not to include it in 2.0. Thanks! I was going to send a status update on this once I finished the

Re: r6rs standard libraries

Hi Andy, Will do, and thanks!! No problem! I'm running into some trouble, though, and I could use your (or somebody's) help. I'm a little shaky on the details with regard to the syntax-case expansion process, but I think the issue is that during the expansion of a single top-level

Re: r6rs standard libraries

Hi everyone, If so, can you make a git branch that (1) adds `library' and `import' to boot-9, then adds the other modules, one-by-one with tests? I've got my finger on the merge trigger :) Done. Take a look at 'wip-r6rs-libraries'. Here's a summary of the changes so far: * The `library'

r6rs standard libraries

Hi Guilers, As mentioned in an earlier email [0], I've been working on implementations for the libraries that make up the so-called R6RS Standard Libraries [1], along with test suites. Where possible, I've tried to wrap existing Guile functionality instead of writing things from scratch.

Re: [PATCH] Unicode string normalization

You might consider checking if the string created by normalize_str should be reduced to the 1-byte-per-character representation.  The procecure scm_i_try_narrow_string could be used for that. Good idea -- I'll add that. Thanks!

Re: [PATCH] Unicode string normalization

Hi Ludovic, Thanks for the review! Looks good to me, please push! Done. +    } +  else w_str = (scm_t_uint32 *) scm_i_string_wide_chars (string); Indentation slightly wrong here. Huh. Looked okay in Emacs, but I've re-spaced everything -- hope that's cleared things up. Regards,

[PATCH] Unicode string normalization

] - http://www.unicode.org/reports/tr15/tr15-31.html [1] - http://www.r6rs.org/final/html/r6rs-lib/r6rs-lib-Z-H-1.html#node_toc_node_sec_1.2 From eb8f72e7d238ee3351411b903898075c2787fc07 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sat, 2 Jan 2010 00:06:23 -0500 Subject

Re: r6rs libraries, round three

Hi all, Find attached a revised and polished version of the `(ice-9 r6rs-libraries)' module I submitted a couple of months ago. This version includes the following changes: * The library transformer code's been cleaned up and compacted (by more than 30%) and now uses a `defmacro' form similar

[PATCH] Unicode general categories

] - http://www.unicode.org/versions/Unicode5.2.0/ch04.pdf [1] - http://www.r6rs.org/final/html/r6rs-lib/r6rs-lib-Z-H-2.html#node_sec_1.1 From f8fef903d535fa9ceb2677ab0c7dacc7692ea0f3 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Thu, 24 Dec 2009 00:25:19 -0500 Subject

Re: More explicit support for Unicode title case

Hi Ludovic, Thanks for the feedback! Please wrap lines to 80 characters. Done. I’d remove this function altogether because with SRFI-14 one can just use ‘(char-set-contains? char-set:title-case chr)’ if that’s what’s intended.  Given the definition of ‘char-set:title-case’, I expect it

Re: r6rs libraries, round three

documentation has been added. Questions? Comments? Regards, Julian From bb83bbd13263aca6a1e8b246fd68ce96f5dcdb43 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Thu, 10 Dec 2009 00:29:11 -0500 Subject: [PATCH 1/2] Support for renaming bindings on module export

Re: r6rs libraries, round three

Hi Andy, Note that quasisyntax is now merged. You can do things without quasisyntax using with-syntax. Of course -- our version of quasisyntax is implemented in terms of with-syntax! I was just being lazy. Your code is remarkably short. That is my initial impression, positive :-) But I

Re: r6rs libraries, round three

Hi Andreas, IIRC, R6RS doesn't /require/ that implementations are able to differentiate bindings from different phases -- e.g. Ikarus essentially ignores phase specifications (implicit phasing -- there were some discussions about that on ikarus-users, which I can't find ATM, but [0] should

Re: r6rs libraries, round three

As I said earlier, I'm happy to provide full documentation for all of this code if the consensus is that I'm on the right track. Any feeling either way on those patches? I'm happy to create a remote tracking branch if that'd make it easier for people to review.

Re: r6rs libraries, round three

/guile-devel@gnu.org/msg04506.html [2] - http://www.mail-archive.com/guile-devel@gnu.org/msg04660.html From adcbc77ca4ca68f26da05a204154d826a832a7b7 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sun, 25 Oct 2009 13:17:40 -0400 Subject: [PATCH] Complete support

build failures from gcc warning about memset

in `scm_gc_calloc', which seems to satisfy the compiler. Regards, Julian From 92ce32eeac2600704fc643ea5f65bda92b2d3bd9 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sun, 25 Oct 2009 13:00:08 -0400 Subject: [PATCH] Resolve warning in gcc-4.3 about transposed parameters

Re: r6rs libraries, round three

Hi Andy, It should work now, though with hacks -- if you manipulate the module-public-interface directly. But perhaps some more baked in support would be useful. Oh, certainly -- as I've learned over these many months, you can do some very interesting things by working with the lower-level

Re: r6rs libraries, round three

Hi all, Besides version, another thing that would be very useful to have native Guile support for is being able to export bindings with names other than the ones given to them within the module -- that is, to be able to rename variables exported as part of the module's public interface in

empty syntax objects

Hi all, This is a weird one. It looks like there's a problem with performing certain operations on syntax objects that wrap the empty list -- I think because such syntax objects are themselves indistinguishable from the empty list. I'm still not sure I fully understand what's going on, but

psyntax error reporting bug

Hi Guilers, I'm no psyntax expert, but it looks like there's a minor typo in our psyntax implementation. In psyntax.scm, at line 1325 (in `chi-macro'), the expression: (syntax-violation #f encountered raw symbol in macro output (source-wrap e w s mod) x) ...should read: (syntax-violation #f

Re: psyntax error reporting bug

Hi Ludo, Andy is the expert, but I think such a patch can’t hurt, so please do! Done! See attached. Regards, Julian From 48128b32d7f9d9613e46b61a3c695d786152fb67 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sun, 18 Oct 2009 17:56:13 -0400 Subject: [PATCH] Fix

Re: r6rs libraries, round three

From: Julian Graham julian.gra...@aya.yale.edu Date: Sat, 26 Sep 2009 14:52:56 -0400 Subject: [PATCH] Initial support for version information in Guile's `module' form. * module/ice-9/boot-9.scm (module-version, set-module-version!, version-matches?): New functions. * module/ice-9/boot-9.scm

r6rs libraries, round three

[1] - http://www.mail-archive.com/guile-devel@gnu.org/msg03259.html [2] - http://article.gmane.org/gmane.lisp.guile.devel/8585 From a1d49c00cd6cc144bf526481e5ba7da6aefa0822 Mon Sep 17 00:00:00 2001 From: Julian Graham julian.gra...@aya.yale.edu Date: Sat, 26 Sep 2009 14:52:56 -0400 Subject: [PATCH

Re: trace examples broken in master

Hi Neil, It works for me with current Git and `,o interp #t'; full transcript below.  Note that this is even when all of the debugging infrastructure modules are auto-compiled; the only code that must _not_ be compiled, for that example to work, is the `rev' procedure. I've cleared my .cache

Re: trace examples broken in master

On Tue, Sep 22, 2009 at 3:57 PM, Neil Jerram n...@ossau.uklinux.net wrote: Not that I'm aware of!  I just tried the transcript again, with current master; no change from what I posted before, except that the version is now 1.9.3, and the stack count incorrect warning has gone. One detail that

build failure in master: zero-length memset

Hi all, I'm getting a build failure on master caused by a warning about a zero-length call to memset (which reminded me of what Ken and Ludo were talking about here [1]). /usr/include/bits/string3.h:82: error: call to ‘__warn_memset_zero_len’ declared with attribute warning: memset used with

Re: trace examples broken in master

Hi Neil, Ack, sorry for not replying sooner -- I've been occupied with switching jobs and moving apartments. This should all be fixed in master now.  Can you have a go and let me know if you still see any problems? Just built from HEAD. The errors I reported earlier are gone, but I'm still

Re: trace examples broken in master

Hey Neil, Thanks for addressing this. Looking forward to trying it out -- it'll be a great help. Regards, Julian On Fri, Aug 14, 2009 at 1:00 PM, Neil Jerramn...@ossau.uklinux.net wrote: Andy Wingo wi...@pobox.com writes: On Tue 14 Jul 2009 10:07, Neil Jerram n...@ossau.uklinux.net

Re: GNU Guile Hackers Meeting?

Hey Mike, Answering this one just for the sake of comedy ;-) I can't make it.  I live in Los Angeles, and I have tickets for the Warped Tour punk festival on the 23rd. Woah, didn't realize that was already happening -- and I've already missed all the east coast dates. Promise me you'll

Re: updated NEWS, release tomorrow

Thanks, Andy (and Neil and Ludovic and everyone else), for the continued hard work! Still can't believe how much progress has already been made. On Tue, Jul 14, 2009 at 5:13 PM, Andy Wingowi...@pobox.com wrote: Hey folks, I've updated the NEWS as best I could for happenings between 1.9.0 and

trace examples broken in master

to figure that out. Regards, Julian From 8751fedfe28eb94cb2974aeb5a2a08310c03d942 Mon Sep 17 00:00:00 2001 Message-Id: 8751fedfe28eb94cb2974aeb5a2a08310c03d942.1247165262.git.julian.gra...@aya.yale.edu From: Julian Graham julian.gra...@aya.yale.edu Date: Thu, 9 Jul 2009 14:44:53 -0400 Subject

Re: r6rs libraries, round two

Hi Andy, Back to your question though, what did you think about my symlink solution[1]? [1] http://article.gmane.org/gmane.lisp.guile.devel/8585 It's fine, although any length suffix of a version specifier can be omitted in the case of a match -- that is, you can do without the version

Re: r6rs libraries, round two

Hi Andy, Your solution of doing whole-program analysis is very much in the spirit of R6RS, but it is not in the spirit of Lisp, in my opinion at least. Well, to be fair, it's not whole-program analysis -- as Neil pointed out, we only need to analyze the library and program headers. But, sure,

Re: r6rs libraries, round two

Hi Neil, I assume the objective here is to allow a Guile program or module to use a portable R6RS library; i.e., specifically, allowing `(use-modules ...)' or `#:use-module (...)' to resolve to an R6RS library.  Is that correct? Actually, my immediate-term goal was to add versioning info to

Re: r6rs libraries, round two

Hi Guilers, With the 1.9 series launched, I wanted to start thinking about R6RS libraries again, since it would be awesome to have some semblance of an implementation ready by October. I think such issues should lead us to have a `:version' option that does just what's needed for R6RS, and

possibility of a new guile-lib release

Hi Andy (and other guile-lib people), So now that the heroic work of launching the 1.9.x series has been done, is there any chance there'll be a guile-lib release to match? Just noticed that 1.6 doesn't play well with Guile 1.9.0 (looks like syncase issues) but that the latest code from the

Re: NEWS entries -- user-visible?

Hi Andy, As mentioned on IRC, I bet there are ways to pitch these changes to make them comprehensible to users. I think you're right to ditch the second one, but for the first and third:    ** Guile now uses Gnulib as a portability aid ** Guile now uses components from Gnulib for portability

Re: r6rs libraries, round two

Hi Neil, I didn't follow why we decided that, but it feels wrong to me.  (It seems to me that Guile should be able to handle loading ((foo) v1) and ((foo) v2) simultaneously as easily as it could handle loading ((foo-v1)) and ((foo-v2)) simultaneously.) I guess I should look up the previous

r6rs libraries, round two

Hi Guilers, I'd like to take another stab at getting R6RS library support in, this time by extending the capabilities of the module system. Here's what I've got in mind to start with: 1. Add an optional `version' field to the module record type * What's a good format here? We could mirror the

Re: 1.9.1 checklist

Hi Andy,  R6RS library support:   No code yet. Julian? :-) Yeah... As I mentioned on IRC, I punted temporarily on that while I was rewriting the parser for my CSS library. Just yesterday, though, I started doing some initial work towards adding version information to modules and the

low-hanging SRFI fruit (SRFI-98)

the GNU ;; Lesser General Public License for more details. ;; ;; You should have received a copy of the GNU Lesser General Public ;; License along with this library; if not, write to the Free Software ;; Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA ;;; Author: Julian

Re: Merging Guile-R6RS-Libs in `master'

Cool!  ;-) The trick is to extend it in a backward-compatible way as much as possible.  But now that we have hygiene and `use-syntax' has been sort-of phased out (Andy?), that should be doable. Perhaps we could create a branch so that you could experiment things? *Urk* You didn't mean

Re: Merging Guile-R6RS-Libs in `master'

Besides that, I don't think that phasing has any practical implication, given the loopholes in the spec -- the set of bindings that a module needs can be determined for *all* phases. That is to say, there is one set of bindings that satisfies the needs of the spec for all phases of evaluation

Re: Merging Guile-R6RS-Libs in `master'

Hi Andy, Guile should probably only support one live version of a module. So Guile's internal module namespace stays the same. Versions are only important when loading files from disk. I propose that we do it like this: Actually, I'd like to disagree here -- maybe I've been writing too much

Re: syncase merged to master

We're fixing all of these. Within the next couple months. We're doing great work, and we should be proud. #scheme can go to hell. Well, *you're* fixing most of them. (For which, by the way, I am obscenely grateful.) On a serious note, though, once the current HEAD makes it into a release, I

Re: r6rs libraries

Hmm, yes, but how about `foo/bar/baz-6.scm'?  Is there a reason to reject it? Well, the part of an R6RS library name that comes before its version is only restricted in that that it must be an identifier -- so a system that relied on filenames to locate libraries could have trouble determining

Re: r6rs libraries

Hi Ludovic, But dot files are traditionally hidden on Unices.  Why not go with `foo/bar/6/baz.scm'? Because my initial plan was to make it possible to have R6RS libraries coexist with Guile modules, using the same directory layout and load system -- and, as per our earlier discussion, numbers

Re: r6rs libraries

Hi Rotty, All R6RS implementations I'm somewhat familiar with (Ikarus, PLT, Ypsilon) do some kind of name mangling when library names contain special characters; e.g. (srfi :6 and-let*) maps to srfi/%3a2/and-let%2a.sls, at least for Ikarus (%-escaped hex of the utf-8 encoding, IIRC). Hey,

Re: r6rs libraries

Hi Guilers, Just wanted to give an update on the status of the library system I've been working on: * As per the discussion above, my implementation uses an implicit phasing approach (i.e., it doesn't do multiple instantiation) along with `(ice-9 syncase)' to handle expand-time evaluation --

Re: r6rs libraries

Hi everyone, (Switching this conversation to guile-devel from guile-user, since it seems more appropriate to this list...) Alright, so I've been studying the van Tonder and Dybvig-Ghuloum implementations and banging my head against chapter 7 of R6RS, all with an eye towards mapping them onto

[PATCH] let*-values in srfi-11 documentation

Hi all, Find attached a small patch that fixes a few instances of a typo in the documentation for SRFI-11 -- the manual was incorrectly referring to `let*-values' as `let-values*'. Regards, Julian From f725da157cabfc9575a6ffe21812182997088370 Mon Sep 17 00:00:00 2001 From: Julian Graham jul

Re: unused return values causing build failures in HEAD

Oops, should've checked Savannah first. Thanks for fixing that! On Sun, Nov 30, 2008 at 11:35 AM, Ludovic Courtès [EMAIL PROTECTED] wrote: Hi Julian, Julian Graham [EMAIL PROTECTED] writes: So I'm trying to build Guile from HEAD after a hard drive wipe, and it looks like the version

unused return values causing build failures in HEAD

Hey everyone, So I'm trying to build Guile from HEAD after a hard drive wipe, and it looks like the version of gcc that ships with Ubuntu 8.10, 4.3.2, now warns when you don't check function return values, which of course breaks Guile's warnings-as-errors build. There are several offending

Re: full moon, vm status update

Hi Andy, My current speculation is that when you compile --with-threads, as I do, that the socketpair between the signal receiving thread and the main thread is not closed after the fork, therefore signals in the child might reach the parent or vice versa, causing random code to

Re: error on startup with latest guile-vm

It appears that the wrong `libguile.so' is being picked up. Assuming you installed the thing with `--prefix=/usr/local' (which is the default), it should be using `/usr/local/lib/libguile.so'. You may need to adjust your LD_LIBRARY_PATH or something. Yep, that was it -- durr, thanks. Sorry

error on startup with latest guile-vm

Hey Andy, I just pulled the latest patches from `vm' and did a make; make install, and got the following the exception when I tried to launch the REPL. I should point out that this is the first time I've been actually able to build the vm branch all the way to installation, so it could very well

Re: Race condition in threading code?

is attached. Let me know if there are any problems with it. Regards, Julian From becf94cd88834d4dbb729346f34d52ca20b50d34 Mon Sep 17 00:00:00 2001 From: Julian Graham [EMAIL PROTECTED](none) Date: Sat, 6 Sep 2008 20:06:17 -0400 Subject: [PATCH] Resolve a deadlock caused by not checking mutex state

Re: Race condition in threading code?

Hi Ludovic, Let me rephrase it: what can happen is that, during the tick, another thread could actually take M, increase `M-level' and mark itself as the owner. After the tick, our primary thread takes `M-lock' back, thinking it now owns M, and goes to sleep; but M is actually already taken

Re: Race condition in threading code?

On Wed, Aug 27, 2008 at 9:14 AM, Julian Graham [EMAIL PROTECTED] wrote: I've seen `srfi-18.test' hang from time to time, but not often enough to give me an incentive to nail it down. :-( I don't think it relates to Han-Wen's GC changes. Crap, I'm seeing some lockups now, too. Sorry, guys

  1   2   >