I wrote something called GDS, back in 1.8 days, that combined some of
the Emacs interaction features that we now have with Geiser, with
step-by-step debugging and breakpoints. You can read about that here:
https://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/Using-Guile-in-Emacs.html#Using-G
On Wed, 16 Feb 2022 at 21:14, Catonano wrote:
>
>
>
> Il giorno mer 16 feb 2022 alle ore 10:54 Neil Jerram
> ha scritto:
>>
>>
>>
>>
>> > As for you creating a web site, I'd prefer such a website to be a
>> > communitarian effort, r
On Wed, 16 Feb 2022 at 09:04, Catonano wrote:
>
> Il giorno lun 14 feb 2022 alle ore 18:01 Vijay Marupudi
> ha scritto:
>>
>> > Is there any interest/possibility to have such a cookbook hosted
>> > within the Guile official documentation (as it is for Guix) ?
>>
>> I personally think that a Cook
I'm afraid arguing by analogy or proverb rarely helps, because the analogy
is usually inaccurate in some way.
Also, what about Horchata? :-)
On Thu, 17 Oct 2019 at 11:53, zx spectrumgomas
wrote:
> Let's hope so. But in Spain we have a proverb: "Blanco y en botella,
> leche". "White and bottle -
On Thu, 20 Jun 2019 at 22:56, Mark H Weaver wrote:
> Hi Ludovic,
>
> Ludovic Courtès writes:
>
> > Mark H Weaver skribis:
> >
> >> I've finished my updates to the NEWS file in preparation for the 2.2.5
> >> release. Feel free to reorganize, edit, or expand on the NEWS entries
> >> as you think
On Fri, 29 Mar 2019, 09:46 David Pirotte, wrote:
> Hi again,
>
> > ...
> > Following your explanation and example, I tried this and thought it
> would work
> > then, but it also failed:
>
> > GNU Guile 2.2.4.1-cdb19
>
> > Enter `,help' for help.
> > scheme@(guile-user)> ,use (system foreign)
> >
On Thu, 28 Mar 2019 at 15:15, Amirouche Boubekki
wrote:
>
> Eventually, I can reproduced the issue with guile-next from guix:
>
> scheme@(guile-user) [1]> (make-c-struct (list '* '*) (list (string->pointer
> "hello ") (string->pointer "there!")))
> $5 = #
> scheme@(guile-user) [1]> (parse-c-struc
Matt Wette writes:
> On 03/27/2018 05:40 AM, Thompson, David wrote:
>> On Mon, Mar 26, 2018 at 5:51 PM, Ricardo Wurmus wrote:
>>> Hi Guilers,
>>>
>>> I wrote a simple SVG-based picture language.
>> Wow! I never would have thought to use sxml to generate svg files. I
>> always thought we would ha
Nice work! I noted a couple of typos :
- documention should be documentation
- miss behaviour should be misbehaviour.
Neil
Original Message
From: David Pirotte
Sent: Wednesday, 22 June 2016 21:46
To: guile-devel
Subject: a draft for the top of the NEWS for 2.0.12
Heya,
Here below a d
On 2014-09-17 17:15, Ian Grant wrote:
When did you last audit these 66,000 lines of intermediate code, which
people are encouraged to run as root?
[...]
ian3@jaguar:~/build/guile-2.0.11$ wc -l Makefile lib/Makefile
libguile/Makefile configure
2373 Makefile
4052 lib/Makefile
3792 libgu
On 2014-09-04 23:37, David Pirotte wrote:
Heya,
ping!
I'm pretty sure it is a guile core and/or a test suite problem, not
related
to corba itself [which as a matter of fact I do not know and do not
use
either :)]
I'd like to solve this problem before to release a guile-gnome-platf
On 2014-08-18 03:14, Ian Grant wrote:
Hi Neil,
Sorry, I am replying to my message because I'm not on guile-devel, it
seems. I'll join later.
Thanks for clarifying that. The misleading statement in the manual is
just above the paragraph you quote: on
https://www.gnu.org/software/guile/manual/htm
On 2014-08-16 00:13, Ian Grant wrote:
Hello Guile types,
Hi Ian,
I have been experimenting with using libguile from within another
byte-code interpreter: Moscow ML. I have a version of Moscow ML with
an GNU lightning interface in which I JIT compile primitives to give
access to libguile funct
On 2014-06-13 17:19, Eli Zaretskii wrote:
From: l...@gnu.org (Ludovic Courtès)
CC: Eli Zaretskii , guile-devel@gnu.org
Date: Fri, 13 Jun 2014 18:04:57 +0200
Like (string-match "^[a-zA-Z]:[/\\]" (getcwd)) ?
>>>
>>> Yes.
>
> But my Git Bash shell on Windows (at work) gives me paths like / let
Eli Zaretskii skribis:
From: l...@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Date: Thu, 12 Jun 2014 21:48:48 +0200
>> >> +(define %null-device
>> >> + ;; On Windows (MinGW), /dev/null does not exist and we must instead
>> >> + ;; use NUL. Note that file system procedures automaticall
On 2014-06-09 20:32, l...@gnu.org wrote:
What’s the name of /dev/null on Windows?
NUL
For example:
C:\Users\nj>echo hello >NUL
C:\Users\nj>
Regards,
Neil
Hi there,
I'm interested in adding support for WebSockets
(http://tools.ietf.org/html/rfc6455) to Guile's web modules. Is anyone
else interested in - or possibly already working on - that?
Thanks,
Neil
On 2014-03-12 06:57, Mark H Weaver wrote:
Andy Wingo writes:
How does this affect libgc?
First of all, it gives an answer to the question of "how much memory
does an object use" -- simply stop the world, mark the heap in two
parts
(the first time ignoring the object in question, the second
Eli Zaretskii writes:
> For my convenience, I prefer to prepare a real ChangeLog entry, then
> copy that to a commit message, which leaves a ChangeLog file around.
> May I add ChangeLog to libguile/.gitignore, so that ChangeLog is not
> flagged by "git status"?
In case you don't already know: to
On 2014-02-20 16:59, Arne Babenhauserheide wrote:
Hi,
I recently experimented with docstrings, and I stumbled over not being
able to define a function which only has a docstring as body:
(define (foo)
"bar")
(procedure-documentation foo)
⇒ #f
Adding a form makes the string
taylanbayi...@gmail.com (Taylan Ulrich B.) writes:
> Hi,
>
> It occurred to me that nil and t are basically just symbols in Elisp,
> just with some magical properties. Like any symbol, they respond to
> symbolp, have a plist, value and symbol slot (although the value slot is
> immutable), etc. T
Andy Wingo writes:
> Hi,
>
> Just thinking aloud here -- Windows has this O_BINARY thing that
> translates CRLF to LF when reading, and LF to CRLF when writing. It
> seems to me to be a useless thing. We already have our own i/o
> abstractions and should deal with CRLF vs LF in Scheme, I think:
Andy Wingo writes:
> On Tue 29 Jan 2013 20:22, Neil Jerram writes:
>
>> (define (read-csv file-name)
>> (let ((s (utf16->string (get-bytevector-all (open-input-file file-name))
>>'little)))
>>
>> ;; Discard possible
Andy Wingo writes:
> What do people think about this attached patch?
>
> Andy
>
>
>>From 831c3418941f2d643f91e3076ef9458f700a2c59 Mon Sep 17 00:00:00 2001
> From: Andy Wingo
> Date: Mon, 28 Jan 2013 22:41:34 +0100
> Subject: [PATCH] detect and consume byte-order marks for textual ports
In case
William ML Leslie writes:
> For most entry-points, there is no extension. When you install your
> program, you normally install it as /usr/bin/foo, rather than
> /usr/bin/foo.[ss|scm|py|js|whatever]. This is the motivation for
> guile-foo symlinks or --lang options. I favour the symlinks slight
Ken Raeburn writes:
> * Require libgc 7.2 or better. Too often the fix to flaky problems
> seems to be "try updating to the latest libgc and see if that fixes
> it", so let's just require it. Or is 7.1 really *that* consistently
> reliable for our use cases on some platforms?
7.2 is required f
Andy Wingo writes:
> Neat :) (Do you pngcrush these? They seem a little slow to serve.)
I just tried running pngcrush on all the .pngs, and didn't get more than
6-8% reduction. So unfortunately it doesn't look like that would help
much.
Thanks for the idea though!
Neil
Mark H Weaver writes:
> Krister Svanlund writes:
>> For example an instance of a class inheriting a class that inherits
>> that defines 'procedure is not applicable.
>
> Looking at the code, it is clear that in order for a GOOPS instance to
> be applicable, it is not enough for to be a
> super
>> For http://ossau.homelinux.net/~neil I do still have all of the raw data
>> including iteration counts, so I could easily implement dividing by the
>> iteration count, and hence allow for future iteration count changes.
>>
>> Is there any downside from doing that? (I don't think so.)
>
> No, I
l...@gnu.org (Ludovic Courtès) writes:
>> My proposal is to rebase the iteration count in 0-reference.bm to run
>> for 0.5s on some modern machine, and adjust all benchmarks to match,
>> removing those benchmarks that do not measure anything useful.
>
> Sounds good. However, adjusting iteration c
Andy Wingo writes:
> On Thu 22 Mar 2012 22:36, Neil Jerram writes:
>
>> It seems like the module has to anticipate the main loop infrastructure
>> that any using programs will use - which isn't a nice solution.
>
> How about, you write your code in such a way tha
l...@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Nala Ginrut skribis:
>
>> On Thu, Mar 22, 2012 at 6:39 AM, Ludovic Courtès wrote:
>>
>>> Hello,
>>>
>>> I had a quick look at ‘wip-nio’, and here are initial comments.
>>>
>>> • epoll is Linux-specific. Any idea how a more multi-platform API
>>>
s no chance of completing (on my build machine) within a day.
Hence for now I'm going to disable the master build.
> Neil Jerram skribis:
>
>> Also, looking at the benchmark graphs at
>> http://ossau.homelinux.net/~neil/bm_master_i.html, there's a bunch of
>> benchmark
Neil Jerram writes:
> FYI, something seems awry in my automatic daily Guile build.
>
> I noticed that the build machine is spending much longer churning away
> than it normally does. Today I found that this is while building the
> master branch, and that it apparently spent
FYI, something seems awry in my automatic daily Guile build.
I noticed that the build machine is spending much longer churning away
than it normally does. Today I found that this is while building the
master branch, and that it apparently spent all day trying
unsuccessfully to
GUILEC language/
Noah Lavine writes:
> Hello,
>
> What ever happened to this issue? Is it considered resolved now, or is
> there more to do?
For my use case it's resolved, in the sense that I really needed a
runtime directory that may not be the same as the source compilation
location; and hence 'current-filenam
Nala Ginrut writes:
> well, I don't believe in copy-paste code too.
> But my vote would be "at least I can trust the official manual"...
I did think it would be nice, a while back, if we could implement a way
of automatically checking that the examples in the manual are still
correct, and that t
l...@gnu.org (Ludovic Courtès) writes:
> Hi Neil!
>
> Neil Jerram skribis:
>
>> Perhaps after all the right thing, for my use case, is something based
>> on (car (command-line)) and (getcwd). I currently have this
>> 'compatibility definition' for G
Sorry for chipping in late to this discussion.
l...@gnu.org (Ludovic Courtès) writes:
> I think it’s often undesirable.
>
> Suppose you want to use ‘current-filename’ in an ‘assert’ macro, for
> instance: what you want is a hint, not an absolute path, since that path
> is likely to be invalid at
Mark H Weaver writes:
> However, (f . (g x y)) is read as (f g x y), so it's impossible for
> 'eval' to distinguish these two cases. Unfortunately, (f g x y) has a
> very different meaning than (apply f (g x y)). The first means to apply
> 'f' to three arguments. The second means to apply 'g'
Rob Browning writes:
> Though if it wasn't too difficult to come up with a reasonable patch,
> we could ask the Debian libgc maintainer to apply it to the older
> version.
I don't yet know if there is such a patch. I can imagine a procedure
for trying to find it: first git bisect to find the ol
Neil Jerram writes:
> On the assumption of using recent libgc git source, I'm still working on
> what Guile fixes, if any, are needed on top of that, for armel. I have
> a set of fixes that works, but it may not be a minimal set.
It turns out that no Guile fixes are needed aft
Hi Rob,
First of all, thanks for pushing 2.0.5 into Debian so quickly!
Rob Browning writes:
> Neil Jerram writes:
>
>> Rob Browning writes:
>
>>> So do I understand correctly that in order for this to work, we'll first
>>> need an updated libgc in Debi
l...@gnu.org (Ludovic Courtès) writes:
> Looks great! I had a glance at the E17 bindings, and I see that the API
> uses raw pointer objects; using “wrapped pointer types” would provide
> type checking, and a nicer UI if you add printers. :-)
That's an excellent point; yes, I'll do that. Using
Andy Wingo writes:
> On Thu 02 Feb 2012 15:44, Catonano writes:
>
>> I'm considering the idea of trying to contribute some Scheme code to
>> guile, and I'm running into some issues with emails, patches, git and
>> the such.
>>
>> What's the common setup you people use ?
>
> I use git, from the c
Andy Wingo writes:
> On Mon 30 Jan 2012 22:32, Neil Jerram writes:
>
>> Following debugging of a strange issue where oFono appeared to be
>> sending a D-Bus signal from the wrong object, but I eventually realised
>> that the problem was in my own code...
>
> The
Following debugging of a strange issue where oFono appeared to be
sending a D-Bus signal from the wrong object, but I eventually realised
that the problem was in my own code...
Neil
>From 02d80ad14c3bb8f89d7ba807dac658be6dd06df1 Mon Sep 17 00:00:00 2001
From: Neil Jerram
Date: Mon,
l...@gnu.org (Ludovic Courtès) writes:
> ... and I forgot to bump the SONAME. :-/
>
> I guess I have to push a 2.0.5 tarball now? Thoughts?
I'm afraid I've forgotten the implications of that...
But congratulations and thanks for the release anyway; for my FFI
hacking I particularly appreciate
Andy Wingo writes:
> Hi Neil,
>
> Thanks for the feedback!
>
> On Sun 22 Jan 2012 00:17, Neil Jerram writes:
>
>> Thing 1 is that (current-filename) can return a relative filename, or a
>> filename with a "./" in its middle
> [...]
>>
>>
Andy Wingo writes:
> Hi,
>
> On Mon 23 Jan 2012 16:45, l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> (add-to-load-path (dirname (dirname (current-filename
>>
>> What about calling it ‘current-file-name’ instead?
I sympathise with that too, although I know I was in
Just in case anyone else is interested in these areas... I had a really
fun time today using the dynamic FFI to hack up Guile code to access
oFono's D-Bus API. It's really great to be able to do this, even if it
might be more efficient in the long run to write a proper C binding.
I've attached t
Andy Wingo writes:
> Hi Neil,
>
> On Sat 14 Jan 2012 22:48, Neil Jerram writes:
>
>> Andy Wingo writes:
>>
>> Of the possibilities above, I think I prefer
>>
>>> (add-to-load-path (dirname (current-source-filename)))
>
> Done. Actu
Andy Wingo writes:
> Then in your script you would (add-relative-load-path ".").
>
> Maybe we need an `add-to-load-path' form that handles the eval-when,
> actually, so it would be
>
> (add-to-load-path (dirname (current-source-filename)))
>
> or something like that. (We'd have to define curre
Rob Browning writes:
> Neil Jerram writes:
>
>> So, just to be clear, the sequence of events for libgc is
>>
>> - start from 9448012a
>> - apply 0001-Debian-7.1-8.patch
>> - apply 0001-Tweaks-for-successful-dpkg-buildpackage-using-libgc-.patch
>
> So d
Nala Ginrut writes:
> Well, I see.
> So the previous discussion didn't make this proc put into Guile?
> Now that so many people interested in this topic.
I'm afraid I can't recall what happened following that thread.
What feels important to me, though, is the elegance of the overall API.
There
Nala Ginrut writes:
> hi guilers!
> It seems like there's no "regexp-split" procedure in Guile.
> What we have is "string-split" which accepted Char only.
> So I wrote one for myself.
We've had this topic before, and it only needs a search for
"regex-split guile" to find it:
http://old.nabble.co
Hi there!
Just in case anyone else is looking at this too, I just wanted to
announce that I'm investigating why the Debian Guile 2.0.3 fails to pass
'make check' on ARM, as can be seen here:
https://buildd.debian.org/status/package.php?p=guile-2.0. Now that
there's a Debian package for Guile 2.0
Ian Price writes:
> Hello guilers,
>
> There's a small aesthetic issue that's been bothering me for a
> while. Namely, newlines aren't treated like other escape sequences when
> printed with WRITE.
>
> scheme@(guile-user)> (write "\n")
> "
> "scheme@(guile-user)>
>
> Now, I can see why this would
Neil Jerram writes:
> The application developer would know if they were using GMP other than
> via Guile, and in that case they'd choose to have GMP use GC
> allocation. Alternatively they might know that their application's use
> of GMP/Guile was not such as to generate
l...@gnu.org (Ludovic Courtès) writes:
> Hi!
>
> Mark H Weaver skribas:
>
>> The main reason I haven't already pushed this patch is that there is a
>> slight complication: when you register custom allocation functions for
>> use by GMP, they get used for _all_ allocation, not just for digits. In
Andy Wingo writes:
> On Tue 24 May 2011 00:23, Neil Jerram writes:
>
>> Neil Jerram writes:
>>
>>> [PATCH 1/5] Fix "occurrances" typos in getopt-long code and test
>>> [PATCH 2/5] Simplify getopt-long handling of option values, esp with
>>
Neil Jerram writes:
> The end result is that guile-tools is a lot shorter and (IMO) sweeter.
>
> Here are the titles of the following patches.
>
> [PATCH 1/5] Fix "occurrances" typos in getopt-long code and test
> [PATCH 2/5] Simplify getopt-long handling of option
David Pirotte writes:
> Looking at 'Procedure Index', for example not really knowing what your
> looking for
> but presumably starting with letter 's', as a 'pure' scheme programmer,
> reaching
> scm-xxx, you'll have to hit more or less 33 times page down [depending on your
> display and browse
* module/ice-9/boot-9.scm (exception-printers): Add 1 to the 0-based
line number.
---
module/ice-9/boot-9.scm |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/module/ice-9/boot-9.scm b/module/ice-9/boot-9.scm
index 60d133f..6130f85 100644
--- a/module/ice-9/boot-9.scm
++
Stefan Israelsson Tampe writes:
> Somewhere in the program I have,
>
> (pk x)
> (pk (caar l))
> (pk (equal? x (caar l)))
>
> It outputs
>
> ;;; (number)
>
> ;;; (number)
>
> ;;; (#f)
>
>
>
> #f is there more to this then meets the eye?
> /Stefan
Well...
scheme@(guile-user)> (equal? 'number
Neil Jerram writes:
> ...by not using its own-rolled getopt, and moving the `list' function
> to a separate script
That one wasn't quite right, please refer to the attached instead.
Neil
>From c106e51707004fb1549add9d1db59c0b45bfed18 Mon Sep 17 00:00:00 2001
From
* module/ice-9/getopt-long.scm (process-options, getopt-long): Change
to "occurrences".
* test-suite/tests/getopt-long.test ("multiple occurrences"): Same
again.
---
module/ice-9/getopt-long.scm |4 ++--
test-suite/tests/getopt-long.test |2 +-
2 files changed, 3 insertions(+), 3
(For use by guile-tools)
* module/ice-9/getopt-long.scm: Use (ice-9 optargs) so we can use
define*.
(process-options): Add stop-at-first-non-option parameter. When
this is true, stop processing when we hit a non-option (so long as
that non-option isn't something that resulted from the un
...by not using its own-rolled getopt, and moving the `list' function
to a separate script
* meta/guile-tools.in: Use (ice-9 getopt-long).
(directory-files, strip-extensions, unique, find-submodules,
list-scripts): Deleted (and moved to new `list' file).
(getopt): Deleted.
(main): Use g
Basically, accumulate values in the `process-options' loop variables,
instead of using set-option-spec-value!
* module/ice-9/getopt-long.scm (option-spec): Delete the `value' slot.
(process-options): Delete `val!loop' and just use `loop' everywhere
instead. When adding an option spec to `fou
This is needed as a prerequisite for the following
don't know how far through the command line we should go with unclumping.
* module/ice-9/getopt-long.scm (expand-clumped-singles): Delete.
(process-options): Add a loop variable to indicate how many elements
at the start of `argument-ls' are
Hi there! While we were discussing the name of guile-tools, back in
March, I wrote:
> I think I might find guile-tools (as is) less bothering if its
> built-in commands (help, version and list) were rewritten as scripts
> themselves. Then it would be clearer that the remaining code in
> guile-to
Andy Wingo writes:
>> Does this code mean that we load the script twice, in the -ds case?
>
> I think so, yes; unfortunately. Fixed. Would this merit a quick 2.0.2,
> you think?
I guess that would be better, if Ludo has time to make the release.
>> Do we go interactive after seeing a -e optio
Hi there,
I was looking today at some recent commits, and noticed a few queries...
In
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=91956a94fe6363cf69d574b56397962ec6ef4468:
+@example
+(while #f (error "not reached")) @result{} #f
+(while #t (break)) @result{} #t
+(while #f
Mark Harig writes:
>> > +The @var{function} is most often a simple symbol that names a function
>> > +that is defined in the script. It can also be of the form @code{(@@
>> > +@var{module-name} @var{symbol})}, and in that case, the symbol is
>> > +looked up in the module named @var{module-name}.
l...@gnu.org (Ludovic Courtès) writes:
>>> It can be put in .dir-locals.el (info "(emacs) Directory Variables").
>>
>> Yeah. In fact it is there, in the root .dir-locals.el, as 72. Is that
>> sufficient?
>
> Oh right, should be enough, yes.
OK, that's fine then; that means we'll naturally asymp
Hi Mark,
FWIW, these patches look great to me; I just have two minor comments,
inline below. It's great to have someone looking at the manual material
with such a careful eye for detail.
Just one meta-thing that occurred to me: can we all agree on a value for
fill-column, so as to avoid spurious
Hi guys
On 12 April 2011 10:55, Ludovic Courtès wrote:
> Hey!
>
> Andy Wingo writes:
>
>> On Sun 10 Apr 2011 00:09, Mark H Weaver writes:
>>
>>> postmas...@stelco.com.mv writes:
This is an automatically generated Delivery Status Notification.
Delivery to the following recipie
Andy Wingo writes:
> It does matter, yes: that suffix is used for looking for a file within
> the load path, and obviously having module/ on the beginning isn't going
> to work. Good catch. You'll have to rebuild everything to get the
> right paths residualized.
>
> Pushed a fix to git.
Great,
l...@gnu.org (Ludovic Courtès) writes:
> Hello Neil,
>
> Neil Jerram writes:
>
>> I think I've successfully cross-compiled Guile (stable-2.0, e309f3bf9e)
>> for my Freerunner phone. However, when I run it, it just keeps
>> allocating memory until the OOM kil
nalaginrut writes:
> I think guile on embedded device would be interesting since it has VM
> now.
Also since it has the FFI - which means being able to access lots of
libraries, without needing to prepare and cross-compile glue code.
> What kernel version your freerunner running?
2.6.34
Rega
Hi there...
I think I've successfully cross-compiled Guile (stable-2.0, e309f3bf9e)
for my Freerunner phone. However, when I run it, it just keeps
allocating memory until the OOM killer kills it:
root@om-gta02 ~ # guile -c 3
Killed
root@om-gta02 ~ # guile
Killed
and if I strace it, the log ends
Andy Wingo writes:
> Hi Neil!
>
> Adding guile-devel; I'm wrong a lot lately, and folks should know ;-)
>
> On Wed 30 Mar 2011 21:11, Neil Jerram writes:
>
>> I saw this change and couldn't fully understand it. Given that you
>> ended up adding GC_disabl
Andy Wingo writes:
> As for explanations... Catch and throw are implemented using fluids and
> prompt and abort. (A discussion of that is here:
> http://wingolog.org/archives/2010/02/14/sidelong-glimpses .) An abort
> can pass arguments to the prompt's abort handler. It does so by pushing
> th
[sorry, this should of course have been CC'd to the list too...]
Hi Andy,
I saw this change and couldn't fully understand it. Given that you
ended up adding GC_disable() and GC_enable() around the GC_malloc()
call, couldn't you just have done that without all the other changes
from "t->" to "t."
Andy Wingo writes:
>>> | GENguile-procedures.texi
>>> | guile: uncaught throw to wrong-type-arg: (#f Wrong type (expecting ~A):
>>> ~S (exact integer (#t # #))
>>> ((#t # #)))
>
> This, it turns out, was something more pernicious, fixed in
> 572eef50c2d902d34427945dd504ba03af666e48.
Than
Andy Wingo writes:
> On Mon 21 Mar 2011 22:50, Neil Jerram writes:
>
>> - "gel" is short; and it's the name of Guile before it was Guile; and
>> suggests sticking things together; and AFAIK isn't already being used
>> for anything else; a
Andy Wingo writes:
> So! My new proposal is "guild".
>
> guild update
> guild compile foo.scm
> guild install fmt
Yes, that's nice.
Neil
l...@gnu.org (Ludovic Courtès) writes:
> 7.x. Best recommendation would be 7.2, which fixes several bugs, but it
> hasn’t been released yet, unfortunately.
>
>> (Note in particular that Guile doesn't build with one of the most recent
>> releases, 7.2alpha4.
>
> Really? What’s the problem with th
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> A few more thoughts...
>
> Andy Wingo writes:
>
>> On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes:
>>
>>> "Andy Wingo" writes:
>>>
bdw-gc 6.8 compatibility (hopefully)
>>>
>>> Aarrrgh. The intent has always been to su
Detlev Zundel writes:
> Hi,
>
> compiling TOT of this branch (commit
> 9dadfa47b07548ff5cf3604067910c8aece93c42 [fix prompt in fix in
> single-value context compilation]) fails like this:
>
> make[2]: Entering directory `/opt/src/git/guile/libguile'
> make all-am
> make[3]: Entering directory `/
Andy Wingo writes:
> On Mon 21 Mar 2011 23:19, Neil Jerram writes:
>
>> Following are 4 simple (I believe) patches that simplify the build.
>> Plus the one at the end (#5) that is only very loosely related to this,
>> because of its mentioning of the $GUILE variable, bu
Andy Wingo writes:
> I have pushed something that causes the stack to be unwound before
> exiting. Please let me know if you still see problems.
Unfortunately, yes. Now when snarf-check-and-output-texi is run, I see:
| GENguile-procedures.texi
| guile: uncaught throw to wrong-type-arg:
I noticed that the filename properties in installed .go files always
begin with "module/". Is this correct and, if not, does it matter?
(For example, and-let-star.go has several occurrences of
module/ice-9/and-let-star.scm where I'd expect just
ice-9/and-let-star.scm.)
Neil
Jan Nieuwenhuizen writes:
[in rearranged order...]
>> -"$(preinstguile)" -l "$(srcdir)/$(snarf_doc).scm" -c "
>> \
>> +"$(top_builddir_absolute)/meta/guile" -l "$(srcdir)/$(snarf_doc).scm"
>> \
>> + -c "
* doc/ref/tools.texi (Executable Modules): Say "guile-tools modules"
instead of "executable modules". Remove obsolete statements about
not ending in .scm, being executable, and beginning with shell
script invocation sequence.
* module/scripts/README: Ditto.
---
doc/ref/tools.texi| 33
It's just one variable definition, and in my opinion it confuses,
rather than helps, the overall build picture to have two names
(preinstguile and meta/guile) for the same thing.
* am/Makefile.am (am_frags): Remove pre-inst-guile.
* am/pre-inst-guile: Deleted.
* doc/ref/Makefile.am: Don't includ
* am/pre-inst-guile (preinstguiletool): Removed.
---
am/pre-inst-guile |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/am/pre-inst-guile b/am/pre-inst-guile
index 7993d15..b7b0d34 100644
--- a/am/pre-inst-guile
+++ b/am/pre-inst-guile
@@ -1,6 +1,6 @@
-## am/pre-inst-
* configure.ac (GUILE_FOR_BUILD): Change normal build value to
'this-value-will-never-be-used'.
---
configure.ac |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index d033420..616bdda 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1487,7 +1
Hi all,
Following are 4 simple (I believe) patches that simplify the build.
Plus the one at the end (#5) that is only very loosely related to this,
because of its mentioning of the $GUILE variable, but I think is a
useful cleanup anyway.
For me, these are part of working towards understanding an
1 - 100 of 1099 matches
Mail list logo
