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" wrote:
> Mark H Weaver writes:
>
> > Julian Graham writes:
> >
> >> It looks lik
.org/final/html/r6rs-lib/r6rs-lib-Z-H-12.html#node_sec_11.2
From 7a207740ffc344c7cd70411bba6c16beaea10818 Mon Sep 17 00:00:00 2001
From: Julian Graham
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 thi
On Thu, Mar 9, 2017 at 4:13 PM, Freja Nordsiek wrote:
> I've written preliminary versionf of all the R7RS libraries along with
> documentation and unit tests for most of the procedures I had to add
> (none for those that were re-exports/renames of existing procedures in
> Guile). Sorry for the bad
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 Guile function? I
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 wrote:
> Howdy!
>
> Find attached a patch that m
cc942aec5e Mon Sep 17 00:00:00 2001
From: Julian Graham
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 o
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 the bug
> that I notice
Hi Wilfred,
Yep! The FSF should have my assignment on file.
On Tue, Sep 20, 2016 at 12:32 AM, Wilfred Hughes wrote:
> Looks good to me (even tests)! Have you assigned copyright papers for Guile?
>
> On 13 September 2016 at 08:42, Julian Graham wrote:
>> Hi Guilers,
>
829c3aff96b1b315ed6fb50c05 Mon Sep 17 00:00:00 2001
From: Julian Graham
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
Hey Mark,
On Fri, Apr 18, 2014 at 5:43 PM, Mark H Weaver 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 just fine.
On Fri, Apr 18, 2014 at 3:21 PM, Julian Graham 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
On Fri, Apr 18, 2014 at 3:20 PM, Andy Wingo 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 compile everyth
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 Andy
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 arg
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 gues
; outside 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
Date: Sun, 18 Sep 20
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 g
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
Hey all,
As part of preparing for the upcoming release, I thought it would be a
good idea to review the contents of the Guile web site at gnu.org.
Here are some initial thoughts I had, in no particular order:
The "What is Guile?" page should be what
http://www.gnu.org/software/guile/ gives you, n
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 se
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 did
help and patience.
Regards,
Julian
From 8714a2a0e5713a57e292cd03f2ef91be167c6ef6 Mon Sep 17 00:00:00 2001
From: Julian Graham
Date: Sun, 10 Oct 2010 01:35:26 -0400
Subject: [PATCH] Improve performance of R6RS records implementation
Reimplement record-type descriptors as vtables for record structs, s
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
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
xt of the test suite 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
Date: Sat, 18 Sep 2010 19
Hey Ludovic,
On Thu, Sep 2, 2010 at 8:49 AM, Ludovic Courtès 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 the culpr
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
> 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 li
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 ;
Hi Guilers,
As promised, I've got an initial draft of the standard libraries
documentation done. Although I tried to avoid reproducing the content
of `r6rs-lib', it's still a bit more verbose, I think, than what we
discussed earlier in this thread (the Texinfo file clocks in at ~83k),
so I could
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
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
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?
>
>
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', contro
. Find attached a
(somewhat 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
Date
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 fou
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 b
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 `mo
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 for
Hi Guilers,
As per Andy's suggestion, I'd like to start adding some documentation
for the R6RS library code Ive been working on, and I wanted to get a
sense of where that documentation should go. My initial feeling is
that there are two documentation sections to be created: A description
of Guile
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
> neces
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 relea
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 f
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 R6R
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 l
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
Hi all,
> ...
>
> Note that the `define-module' form at the top is related to the error
> -- without it, both examples work just fine. (Wild speculation: Is it
> possible that in the context of changes to the "current module" that
> `define-syntax' puts bindings in a place different from where t
Hello again,
> Does this sound plausible? I spent most of this past weekend trying
> to grok this and work around it (via various `eval'-based
> incantations) without much luck. (The weird part is, I don't recall
> this happening with my old `(ice-9 r6rs-libraries)' module
> implementation, but
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 expression
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'
Hi Andy,
> I also think we should have `library' and `import' in the basic
> environment. In order to do this I would like for them in boot-9.scm,
> not in a separate module, and implemented in terms of syntax-case.
>
> Implementing `library' in terms of syntax-case will allow `library' to
> expa
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. Speakin
> 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!
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,
J
] - 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
Date: Sat, 2 Jan 2010 00:06:23 -0500
Subject: [PATCH] Support for
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 to
Hi Mike,
> Cool. I have two very minor and pedantic suggestions. You say that
> it will return a "one- or two-letter name". I'm pretty sure that
> this code will always return a two-letter name and not the one-letter
> general category.
Yes, of course you're right -- uc_general_category_name o
n
[0] - 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
Date: Thu, 24 Dec 2009 00:25:19 -0500
Subject: [PATCH] Suppor
> Thanks for all. I wrapped your commit messages, detabbed the files, and
> did some minor editing. Please look at the diffs relative to your
> patches. But other than that, thanks very much! :-))
No, thank /you/! ¡Que buena sorpresa!
On a related note, I assume Emacs' `scheme-mode' has been add
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 i
there are no
issues, commit it -- or let me know and I'll do it myself? (I've
gotten a significantly more confident with git over the past few
months.)
Thanks,
Julian
[0] - http://www.unicode.org/versions/Unicode5.0.0/ch05.pdf#G21180
From 82052a10da40a6d814ab30a944859c83bb6fe68e Mon Sep
nsive documentation has been added.
Questions? Comments?
Regards,
Julian
From bb83bbd13263aca6a1e8b246fd68ce96f5dcdb43 Mon Sep 17 00:00:00 2001
From: Julian Graham
Date: Thu, 10 Dec 2009 00:29:11 -0500
Subject: [PATCH 1/2] Support for renaming bindings on module export.
* module/ice-9/boot-
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]
> sho
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
> 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.
earlier, I'm happy to provide full documentation for all of
this code if the consensus is that I'm on the right track.
Regards,
Julian
[1] - http://www.mail-archive.com/guile-devel@gnu.org/msg04506.html
[2] - http://www.mail-archive.com/guile-devel@gnu.org/msg04660.html
From
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
check on the size parameter in
`scm_gc_calloc', which seems to satisfy the compiler.
Regards,
Julian
From 92ce32eeac2600704fc643ea5f65bda92b2d3bd9 Mon Sep 17 00:00:00 2001
From: Julian Graham
Date: Sun, 25 Oct 2009 13:00:08 -0400
Subject: [PATCH] Resolve warning in gcc-4.3 about transposed para
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 `def
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 suf
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
Date: Sun, 18 Oct 2009 17:56:13 -0400
Subject: [PATCH] Fix typo in psyntax.
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
Hi Ludovic,
Naive question (and I realize I'm a bit late here): What if there are
bindings in the current module that need to be present for expansion
and compilation to succeed? I ask because I'm working on a macro that
transforms R6RS library expressions, which contain nested `define'
calls, in
6481e5ba7da6aefa0822 Mon Sep 17 00:00:00 2001
From: Julian Graham
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.
*
his magic hasn't been added to
`primitive-load' (or some other function that operates on absolute
paths)?
Regards,
Julian
[1] - http://www.mail-archive.com/guile-devel@gnu.org/msg03259.html
[2] - http://article.gmane.org/gmane.lisp.guile.devel/8585
From a1d49c00cd6cc144bf526481e5ba7da6aefa
On Tue, Sep 22, 2009 at 3:57 PM, Neil Jerram 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 I didn't say befo
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 .ca
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 c
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
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 Jerram wrote:
> Andy Wingo writes:
>
>> On Tue 14 Jul 2009 10:07, Neil Jerram writes:
>>
>>> but the right thing to do is to fix the scm_set
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
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 Wingo wrote:
> Hey folks,
>
> I've updated the NEWS as best I could for happenings between 1.9.0 and
> 1.9.1. The
. Not sure
where to look 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
Date: Thu, 9 Jul 2009 14:44:53 -0400
S
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 a
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,
su
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
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 d
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 guile-
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
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 previ
Hi Neil,
> Am I correct in thinking that you can commit this yourself? - subject
> to Savannah coming back up, of course. If so, please do that after
> incorporating the following points.
Can I? As far as I know I haven't been granted the appropriate
permissions, but I'll look into it.
> That
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
> Looks good to me, please go ahead.
Find attached a patch that includes the implementation previously
attached, plus unit tests and additions to the NEWS and modules.texi
files.
Regards,
Julian
From a1e4bcb30b80199de6f2cd620d950d04e0734592 Mon Sep 17 00:00:00 2001
From: Julian Graham
D
. See 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
;;; Auth
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 module-
I second the Yy!
On Fri, May 22, 2009 at 10:39 AM, Andy Wingo wrote:
> Hi!
>
> I'm catching up with mail. On my syncase-in-boot-9 branch, I enabled
> compilation of srfi-18 and fixed a bug in it regarding multiple-value
> returns. Now I just ran the srfi-18 test like 100 times in a row and i
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
>> 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
>> e
> 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 m
Hi Ludovic,
> That means, for instance, that module versioning could first be
> implemented in Guile's module system, which would then simply be used by
> the `library' form.
>
> The main differences between these two module systems are module
> versioning, and phase separation. Fortunately, R6RS
1 - 100 of 198 matches
Mail list logo
