-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I posted more details on guile-devel. Perhaps this was the wrong list?
When transforming SXML to XML, namespaces don't seem to be handled
properly:
#!/usr/bin/guile -s
!#
(use-modules (sxml simple))
;; An XML with two namespaces (one
Hi,
I've embellished my proposed patch a bit:
- use values resp. call-with-values instead of passing around
lists.
This was one thing I didn't like about my first patch candidate:
the namespace --> ns abbreviation lookup had two things to return,
for noe the abbreviation, and whethe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 21, 2015 at 11:24:03AM +0200, Ricardo Wurmus wrote:
> Hi Tomás,
>
> to...@tuxteam.de writes:
>
> > When transforming SXML to XML, namespaces don't seem to be handled
> > properly:
> >
> [...]
> >
> > The problem is that SXML used the conc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 22, 2015 at 04:29:32PM +0200, Ricardo Wurmus wrote:
> >> Since xml->sxml accepts a namespace alist I suppose it would make sense
> >> to extend sxml->xml to do the same.
>
> Attached is a minimal patch to extend "sxml->xml" such that it ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Apr 23, 2015 at 09:04:46AM +0200, Ricardo Wurmus wrote:
>
> to...@tuxteam.de writes:
>
> > What's yet missing (as far as I can read off the diff) is a way to
> > "dream up" an abbreviation when it's not in the namespaces alist.
>
> True.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 22, 2015 at 04:29:32PM +0200, Ricardo Wurmus wrote:
> >> Since xml->sxml accepts a namespace alist I suppose it would make sense
> >> to extend sxml->xml to do the same.
>
> Attached is a minimal patch to extend "sxml->xml" such that it ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Apr 25, 2015 at 10:25:09PM +0200, to...@tuxteam.de wrote:
[...]
> Reading again Oleg Kiselyov's paper[1] I understand that SXML can, as does
> XML have namespace abbreviations (called there user-ns-shortcut). It's not
> exctly the same thing,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Aug 28, 2015 at 09:47:51PM -0400, Jamil Egdemir wrote:
> Hi Guys,
>
> I just pulled the latest from the git repo and the build failed on
> OpenBSD 5.6 (output from dmesg is all the way at the bottom if that
> helps):
>
> $ git clone http://gi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 07, 2015 at 01:58:48PM +0100, Atticus wrote:
> So I wanted to try out gnu guix and thus make myself more familiar with
> guile first. While running some tests I encountered a problem/bug with eq?:
>
> $ guile -v
> guile (GNU Guile) 2.1.1
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 08, 2015 at 02:30:42PM +0100, Atticus wrote:
[...]
> Yes you are right that the implementation may treat it as non #f if both
> arguments refer to the same object. In r5rs (and also r6rs) (eq? '(a)
> '(a)) is unspecified (r5rs, page 19) a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 05, 2016 at 10:24:35AM +0800, Chaos Eternal wrote:
> On Tue, Jan 5, 2016 at 3:14 AM, Nala Ginrut wrote:
> > Hi Mark!
> > Thanks for all the advices.
> >
> > Here's the new patch according to your advices.
> > Include:
> > 1. Added new proc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 03, 2016 at 12:36:15PM -0500, Mark H Weaver wrote:
> Nala Ginrut writes:
>
> > Is there still problem? I'm fine with the patch, and I'm expecting to
> > merge it ASAP. Anyway, please don't hesitate to tell me if there's still
> > any prob
share/guile/site" "/usr/share/guile"))
> --8<---cut here---end--->8---
I can confirm half of it :-)
I mean: the double entry "foo" for %load-path in your first result
above doesn't happen for me. Could that be a typo?
As f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 23, 2016 at 09:32:16PM +0200, Andy Wingo wrote:
> See thread here as well:
> http://thread.gmane.org/gmane.lisp.guile.devel/17709
>
> I like Ricardo's patch but have some comments here:
> http://article.gmane.org/gmane.lisp.guile.devel/183
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jul 13, 2016 at 03:24:03PM +0200, to...@tuxteam.de wrote:
[...]
> What is missing? From my point of view:
>
> - At xml->sxml time, the user doesn't know which namespaces
>are in the xml. So it would be nice if the XML parser
>could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 14, 2016 at 12:10:17PM +0200, Andy Wingo wrote:
> Hi :)
>
> On Wed 13 Jul 2016 15:24, to...@tuxteam.de writes:
>
> > Referring to Oleg Kiseliov's paper [1], there are actually three
> > things involved:
>
> This summary is helpful, thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Oct 10, 2016 at 06:39:47PM +0200, Ludovic Courtès wrote:
> Hello!
[...]
> Furthermore, AFAICS, the above logic is redundant with what the kernel
> does anyway. That is, in a single-threaded program,
>
> mask = umask (0);
> umask (mask);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Mar 18, 2017 at 01:10:58AM +, Zefram wrote:
[...]
> Where did you get the idea to use a non-linear year numbering? What's
> your opinion of SRFI-19's (lack of) text on this matter? You should
> consider the possibility of changing your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 23, 2017 at 07:59:04PM +, Joshua Branson wrote:
>
> I can confirm this bug. Eshell accepts (defun hello nil (print “Hello"))
> And (hello) works properly.
>
> M-x guiler
>
> ,languages elisp
>
> (defun hello nil (print “Hello”))
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 03, 2018 at 04:31:23PM -0300, David Pirotte wrote:
> Hi Ludovic,
>
> > > It is perfectly fine, on the opposite side, to ask advanced scheme users
> > > (who
> > > would want to, but I really don't see the point) configure guile s the
> >
On Mon, Feb 04, 2019 at 09:44:02PM +0100, Ricardo Wurmus wrote:
> Hello!
>
> I just looked at this again and I think I came with something useful.
> Here’s some context:
[...]
> Attached is a patch that does the requested things. The parser
> procedures like FINISH-ELEMENT have access to all th
On Tue, Feb 12, 2019 at 03:34:06PM +0400, Андрей wrote:
> Good day!
>
> The docstring of `reverse-list->string` proc says:
> ```
> scheme@(guile-user)> (help reverse-list->string )
> `reverse-list->string' is a procedure in the (guile) module.
>
> - Scheme Procedure: reverse-list->string chrs
>
ning: possibly unbound variable `xml->sxml'
;;; note: source file ./sxml/simple.scm
;;; newer than compiled /usr/local/lib/guile/2.2/ccache/sxml/simple.go
;;; found fresh local cache at
/home/tomas/.cache/guile/ccache/2.2-LE-8-3.A/home/tomas/guile/sxml-fix/sxml/simple
Hi,
after mulling over it for a while, I think it's time to take
a step back and think a bit about where we'd like to go with
this.
Note that I'm ignoring technical details (the fact that the
SXML, and thus the XML serialization now has namespace declarations
everywhere down the path instead of j
On Sun, Jun 16, 2019 at 08:16:29PM +0300, Abdulrahman Semrie wrote:
>
> I am using the pattern [\\[\\]a-zA-Z]+ to match a string with left or right
> bracket in it. However, the string-match function doesn’t match the ‘]’
> character. To demonstrate with an example, try the following funciton:
>
On Tue, Jun 18, 2019 at 07:08:06AM -0400, Mark H Weaver wrote:
> Hi,
>
> Abdulrahman Semrie writes:
>
> > I am using the pattern [\\[\\]a-zA-Z]+ to match a string with left or
> > right bracket in it [...]
> It turns out that there are several flavors of regular expressions in
> common use, wit
On Sat, Nov 16, 2019 at 09:41:05PM +0100, Andy Wingo wrote:
> Given the following example, using (rnrs unicode):
>
> (string-foldcase "ΜΈΛΟΣ")
Good catch. I think there's even a worse example: dotless
and dotted I [1]. Here it seems even impossible to do
up- and downcase correctly without knowi
On Wed, Nov 27, 2019 at 12:05:34PM +, Zefram via Bug reports for GUILE,
GNU's Ubiquitous Extension Language wrote:
[...]
> But please don't get sidetracked. This wasn't a feature request for
> "#eof" [...]
To be fair, you contributed strongly to this side-tracking. By waving
a big red flag
8.3.0.
FWIW, I just tried with guile 2.9.5 and the compile terminates:
tomas@trotzki:~$ guile /tmp/zack.scm
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /tmp/zack.scm
;;; compiled /home/tomas/.cache
On Tue, Mar 10, 2020 at 11:05:24AM +0100, Jan Synacek wrote:
> I have the following backtrace:
>
> Backtrace:
> In ice-9/boot-9.scm:
> 1736:10 9 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
>8 (apply-smob/0 #)
> In ice-9/boot-9.scm:
> 718:2 7 (call-with-promp
On Sat, Apr 25, 2020 at 11:15:40PM +0200, Bengt Richter wrote:
> I'm hoping this is the right place to report this bug :)
>
> To reproduce, guile -c '(format #t "~s\n" (integer-length 0))'
> Expected result if correct: 1
> Observed result: 0
>
> The following is to support the opinion that 1 is t
On Sat, May 16, 2020 at 12:29:54PM +0200, Jan Synacek wrote:
> Consider the following code snippet running on Guile-3.0.2:
[...]
>
[...]
> (event (@ (number 2) (name KeyPress))
> Attributes 'number' and 'name' are in reverse compared to the original
> xml. On the other hand, 'type' and '
On Sat, May 16, 2020 at 02:27:15PM +0200, Jan Synacek wrote:
[...]
> > just imagine another XML processor in the middle changing
> > attribute order. It would be spec compliant. What now?
[...]
> In the middle of the first processor reading the file?
No, I was thinking much simpler than that.
On Tue, Jun 23, 2020 at 12:51:23AM +0200, Sebastian Miele wrote:
> Guile 3.0.3. The reference manual and the docstring of number->string
> say: "If N is inexact, a radix of 10 will be used." But that is not what
> happens, e.g.,
>
> (let ((x 4.0)) (and (inexact? x) (number->string x 3)))
>
> ev
On Fri, Sep 11, 2020 at 03:31:24PM +0700, Erik Dominikus wrote:
> Dear author(s) of the Guile 3.0.x compiler,
>
> Background: I would like to report a problem that I found while trying
> to write a simple web server with get-string-n, sxml simple, and web
> server.
>
> I have traced and reduced t
On Sat, Sep 12, 2020 at 10:59:23PM +0200, pinoaffe wrote:
> Dear guilers,
>
> When using with-output-to-string, the output of external processes
> started using system* and the like is not redirected to the temporary
> port. As far as I can tell, it just redirects things written/displayed
> from w
On Sat, Jan 16, 2021 at 11:42:18PM +0100, paul.eb...@mail.de wrote:
> Hello everyone, I'm very sorry, if this is the wrong mail adress
> for my problem, but I couldn't find another to seek for help. I
> just thought that you are probably the expert for my question and
> are maybe willing to hel
On Sun, Jan 17, 2021 at 09:18:59PM +0100, Dr. Arne Babenhauserheide wrote:
>
> paul.eb...@mail.de writes:
>
> > is there a way to install Guile or Make on Manjaro without an internet
> > connection and without having already installed one of them?
>
> You’ll need to build and install make once w
On Fri, Jan 22, 2021 at 09:47:24AM -0500, jbranso--- via Bug reports for GUILE,
GNU's Ubiquitous Extension Language wrote:
> Ricardo Wurmus writes:
>
> > Hi Joshua,
> >
> >> When I look at
> >>
> >> #+BEGIN_SRC scheme
> >> (define (thunk)
> >>(lambda (x)
> >> x))
> >> #+END_SRC
> >
> >
On Thu, Feb 11, 2021 at 09:54:38PM +0100, Ricardo Wurmus wrote:
> This program sometimes causes Guile 3.0.5 to segfault:
>
> (define a (expt 2 (expt 3 (expt 4 2
> (display (remainder a 10))
> (display "\n")
>
> And sometimes this program doesn’t terminate. Here’s an example
> s
On Tue, Oct 12, 2021 at 10:26:22AM +0200, Alexey Abramov via Bug reports for
GUILE, GNU's Ubiquitous Extension Language wrote:
> Hi,
>
> I agree that it is not a complient http response,
According to The Book [1] ;-) there should be at least one
space (SP) (as far as I understand this is really
On Sun, Nov 13, 2022 at 02:15:43AM +, jbranso--- via Bug reports for GUILE,
GNU's Ubiquitous Extension Language wrote:
> November 12, 2022 12:58 PM, "Jean Abou Samra" wrote:
>
> >> Le 12 nov. 2022 à 18:50, Joshua Branson via Bug reports for GUILE, GNU's
> >> Ubiquitous Extension
> >> Langua
On Fri, Nov 18, 2022 at 02:49:05PM +1000, Andrew Whatson wrote:
> Hi Nate,
>
> Thanks for reporting this! I'm able to reproduce on my systems, and
> have identified the culprit:
[250k calls to close()]
Well spotted.
Here [1] is a good discussion on the problem. Spoiler alert:
there is no nice,
On Sun, Nov 20, 2022 at 06:24:57PM +0100, Ludovic Courtès wrote:
> Hi,
>
> Andrew Whatson skribis:
>
> > Forcibly closing file descriptors like this shouldn't be necessary if
> > the application has properly opened descriptors with the FD_CLOEXEC
> > flag. It would be good to get input from som
e) just installed from the repositories.
Hi,
this is Debian GNU/Linux, x86_64, but a self-compiled Guile:
| tomas@trotzki:~$ guile
| GNU Guile 3.0.8.57-bc3b1
| Copyright (C) 1995-2022 Free Software Foundation, Inc.
|
| Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
|
On Tue, Jan 03, 2023 at 05:57:19PM +0100, Sascha Ziemann wrote:
> The following throws an error:
> guile -c '(make-vector)'
>
> But the evaluation of '(make-vector)' in the REPL generats just a warning:
>
> ;;; :1:0: warning: possibly wrong number of arguments to `make-vector'
>
> and seems to e
On Tue, Jan 03, 2023 at 09:00:48PM +0100, Liliana Marie Prikler wrote:
> Hi folks,
>
> Below some unexpected behaviour observed in Guile 3.0.8, but it also
> dates back to 2.2.7 and possibly earlier versions.
>
> scheme@(guile-user)> ,use (web uri)
> scheme@(guile-user)> (string->uri "file:///hom
ment to disable.
> ;;; compiling /home/amaya/tmp/guile-compiler-bug.scm
> ;;; WARNING: compilation of /home/amaya/tmp/guile-compiler-bug.scm failed:
> ;;; not found 22
>
> Compiler reports confusing message here: `not found 22’.
Bizarre. Can confirm
tomas@trotzki:~/foo$ vim buggy.scm
On Mon, May 01, 2023 at 10:44:18AM +0800, Christopher Lam wrote:
> The source seems to be sxpath.scm -- see "yikes" error which triggers when
> n is -2 -4 -6 etc. I don't know how to build guile from sources and cannot
> debug further.
>
>
> (define (node-pos n)
> (lambda (nodeset)
> (cond
It worked for me too.
On Sat, Sep 23, 2023 at 09:19:54AM +0530, ahmad khizir wrote:
> Not working for me, i can share the screenshot.
Perhaps better if you describe what you are trying (how are
you downloading, perhaps whether you are in a company or
country which might enforce network restrictio
ou know.
Thank you for the details!
You may try the "-S" options to wget: this will print the HTTP
headers, which might help in identifying the problem.
If I do that, this is what I see:
| tomas@trotzki:/tmp$ wget -S https://ftp.gnu.org/gnu/guile/guile-3.0.9.tar.gz
| --202
On Tue, Feb 27, 2024 at 08:14:58PM +, Zefram via Bug reports for GUILE,
GNU's Ubiquitous Extension Language wrote:
> Trying out the basename function in Guile 3.0.9:
>
> scheme@(guile-user)> (basename "foo/bar")
> $1 = "bar"
> scheme@(guile-user)> (basename "foo/bar" "r")
> $2 = "ba"
> scheme
On Tue, Aug 13, 2024 at 07:06:09PM -0400, Bryce Moore wrote:
> I know it's nonsensical, but (set! display #f) in a fresh interpreter
> causes an infinite loop.
>
> Interrupting with Ctrl+C exits guile.
>
> scheme@(guile-user)> (set! display #f)
> While reading expression:
> Wrong type to apply: E
archives. I'm
> surprised it's not fixed in 1.6.0, but maybe it's because I never sent
> the patch in...
Thanks a zillion. I'll try this out when out of crunch mode.
I'll keep you informed
Regards
-- tomas
___
Bug-guile maili
Banned CD! Government don't want me to sell it. See Now #
woody incurred precipitate jar confiscate anemone cheyenne nebula signify melon nonce beloit
hackney innermost send gainful admission deane susan downgrade carla babylon filamentary applicable conglomerate brownell floppy apology greet
On Sat, Feb 01, 2025 at 09:10:04PM +0100, Tomas Volf wrote:
>
> Hello,
>
> I think I found a bug in the htmlprag module in guile-lib. When parsing
> attributes, the values are not properly decoded:
>
> --8<---cut here---start-&g
Hi Guys,
I am trying to package guile 3.0.7 into Fedora but I encountered a problem.
In sources, there is a header lib/libc-config.h and then there is
preprocessor condition for presence of __attribute_maybe_unused__ macro.
This macro is newly defined in the latest version of glibc which we have in
Hi,
There is a bad address specified in the license of
module/language/elisp/compile-tree-il.scm file in version 3.0.7. I am
attaching a patch to fix this.
commit 5a888dc8cba740718d302e4e759b28bc19a9d06c
Author: Tomas Korbar
Date: Thu Jul 22 13:02:56 2021 +0200
Fix address of FSF
diff
Both macros were missing a quote for the procedure call, causing the
actual return value to be compiled into the ftw.go, instead of the
procedure call. Snippet from disassembly of ftw.go does confirm that:
55(make-immediate 2 3990) ;; 997at
ice-9/ftw.scm:319:46
56
it over from here, that would
be great. :)
>
> Mike Gran
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
is still on the radar.
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
3.0.8-2
all Documentation for Guile 3.0
ii guile-3.0-libs:amd643.0.8-2
amd64Core Guile libraries
Thanks for all the work
--
Tomas
lloda writes:
> I think this is another dupe of https://debbugs.gnu.org/58154.
Highly possible. Like Ricardo I cannot reproduce this with a local build
I made from the tip of the repo. (I saw the same segfault using list-ref
with the debian 3.0.8 version FWIW.)
--
Tomas
Mike Gran writes:
Hello,
> I haven't forgotten about this. My linux devel box died.
>
> Maybe someone else can make the push, otherwise, I'll be back in business in
> a couple weeks.
Just a polite ping regarding this patch.
Thank you and have a nice day,
Tomas Volf
On modern file-systems (BTRFS, ZFS) it is possible to copy a file using
copy-on-write method. For large files it has the advantage of being
much faster and saving disk space (since identical extents are not
duplicated). This feature is stable and for example coreutils' `cp'
does use it automatica
Until now, the ./meta/guile was not mentioned anywhere, and therefore it
was not obvious how to run the locally compiled Guile without installing
it.
While modifying the file, I took the liberty to also mention a bit about
compiling Guile using Guix.
Finally, the header lines where cleaned up, en
Extend the documentation for (ice-9 match) module with explanations of
some of the patterns and also provide more examples for them. That
should make it more useful for people trying to use the module for the
first time just based on the documentation.
* doc/ref/match.texi (Pattern Matching): Exp
While the `.' might be correct from a grammatical point of view (I do
not know), it turns the example into invalid scheme code, which is not
ideal. New users (like me) might try to copy the whole line and wonder
why it does not work (like I did). So delete it.
* doc/ref/srfi-modules.texi (SRFI-1
Until now, the ./meta/guile was not mentioned anywhere, and therefore it
was not obvious how to run the locally compiled Guile without installing
it.
While modifying the file, I took the liberty to also mention a bit about
compiling Guile using Guix.
Finally, the header lines where cleaned up, en
WDYT?
Modified as agreed on irc. I am not convinced on the -P, but I defer to your
judgment on this.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
On modern file-systems (BTRFS, ZFS) it is possible to copy a file using
copy-on-write method. For large files it has the advantage of being
much faster and saving disk space (since identical extents are not
duplicated). This feature is stable and for example coreutils' `cp'
does use it automatica
On modern file-systems (BTRFS, ZFS) it is possible to copy a file using
copy-on-write method. For large files it has the advantage of being
much faster and saving disk space (since identical extents are not
duplicated). This feature is stable and for example coreutils' `cp'
does use it automatica
find time to actually form an
opinion based on facts.
Have a nice day,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
ile "/dev/null")), I would not
expect invalid value in an interpreted language to cause a segfault. If the
value is indeed invalid, it should throw an error.
Original report: https://emacs.ch/@kakafarm/112075808549752692
Have a nice day,
Tomas Volf
--
There are only two hard things
or 'auto case:
CoW ---fail--> copy_file_range ---fail--> current copy ---fail--> FAIL
For 'never case:
copy_file_range ---fail--> current copy ---fail--> FAIL
Is that an accurate summary? Or did you mean only as a fallback for the CoW, so
only for 'aut
The current recommendation of `list-copy' is not right and does not lead
to preserving the original list:
scheme@(guile-user)> (define x (list (cons 'a 1) (cons 'b 2)))
scheme@(guile-user)> (define y (list-copy x))
scheme@(guile-user)> (assq-set! y 'b 3)
$1 = ((a . 1) (b . 3))
If user does not have LANG or LC_ALL set (as does often happen in
various sandboxes) glibc will just install C locale. That is fine (and
permissible by POSIX), however in Guile's context it is of a mixed
usefulness due to the absence of UTF-8 support.
This commit changes the locale auto-installat
`tmpnam' is a deprecated procedure that can be excluded during a
configure (`--disable-tmpnam'). There currently was a single test
relying on it, and therefore failing is such configuration. This commit
switches to mkstemp instead.
* test-suite/tests/posix.test ("system*"): Use mkstemp instead o
According to the previous wording, omitting all optional arguments led
to empty interface. That however was not the case and was only a
documentation bug (as confirmed by wingo on IRC). So let us fix that.
* doc/ref/api-modules.texi (Using Guile Modules): Fix implication of
omitting optional arg
* doc/ref/api-modules.texi (Using Guile Modules): Document #:hide.
---
doc/ref/api-modules.texi | 29 ++---
1 file changed, 18 insertions(+), 11 deletions(-)
diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index 9f2bba02d..efe739a25 100644
--- a/doc/ref/ap
Document the #:hide argument. Correct text for implication of leaving
all optional arguments out.
Tomas Volf (2):
doc: Document #:hide.
doc: Fix implication of omitting optional arguments.
doc/ref/api-modules.texi | 29 ++---
1 file changed, 18 insertions(+), 11
According to the previous wording, omitting all optional arguments led
to empty interface. That however was not the case and was only a
documentation bug (as confirmed by wingo on IRC). So let us fix that.
* doc/ref/api-modules.texi (Using Guile Modules): Fix implication of
omitting optional arg
* doc/ref/api-modules.texi (Using Guile Modules): Document #:hide.
---
doc/ref/api-modules.texi | 29 ++---
1 file changed, 18 insertions(+), 11 deletions(-)
diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index 9f2bba02d..efe739a25 100644
--- a/doc/ref/ap
(lambda ()
> -(with-error-to-port port
> - (lambda ()
> -(system* "sh" "-c" "echo bong >&2"
> + (system* "sh" "-c" "echo bong >&2&quo
ASS
That does not seem to be allowed by SRFI-64. I do not believe this is limited
to test-assert, I managed to reproduce with test-equal as well.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
pected-error:
+ foo
actual-error:
+ (bar)
result: PASS
According to feedback from mastodon it is not really implemented. That does not
seem to be documented. Maybe it would be better to just not export it? Or it
should throw 'not-implemented instead of just passing?
Have a nice day
= #
Notice that by importing srfi-1 the list-index changes to the documented one.
You are right that the "default" list-index indeed does not seem to be
documented. It also uses `eq?' for comparisons and does not allow changing
that.
I hope this sheds some light on the problem.
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
x"))
However it does not:
;;; ("")
Have a nice day
Tomas Volf
4388:12 1 (_)
In srfi/srfi-64/testing.scm:
375:14 0 (test-on-bad-end-name-simple _ _ _)
srfi/srfi-64/testing.scm:375:14: In procedure test-on-bad-end-name-simple:
test-end x does not match test-begin y
Have a nice day
Tomas Volf
#t)
(pk (test-result-kind))
(test-end)
Leading to:
;;; (xpass)
;;; (pass)
Have a nice day
Tomas Volf
olfsden/tests/srfi-64/test-approximate-throw.srfi64test:
7:0 2 (_)
In srfi/srfi-64/testing.scm:
677:16 1 (_ _ #f)
In unknown file:
0 (real-part #f)
ERROR: In procedure real-part:
In procedure real-part: Wrong type argument in position 1: #f
Have a nice day
Tomas Volf
(test-runner-null)))
(test-runner-current r)
(test-runner-on-bad-end-name! r
(λ (runner begin-name end-name)
(pk begin-name)))
(test-begin "x")
(test-assert #t)
(test-end "y"))
But it does not:
;;; ("y")
Have a nice day
Tomas Volf
(- expected error))
>(<= test-expr (+ expected error
However the test-name is evaluated multiple times:
(use-modules (srfi srfi-64))
(test-begin "x")
(test-approximate (pk "t") 1 1 0)
Leading to:
;;; ("t")
;;; ("t")
Have a nice day
Tomas Volf
-name is evaluated multiple times:
(use-modules (srfi srfi-64))
(test-begin "x")
(test-eqv (pk "t") #t #t)
Leading to:
;;; ("t")
;;; ("t")
Have a nice day
Tomas Volf
ting full log to "x.log")
;;; (t-a)
;;; (t-b)
Notice that in the second part, t-b is executed despite not supposed to be on
the run list.
Have a nice day
Tomas Volf
syntax-violation:
Syntax error:
unknown location: lambda: bad lambda in form (lambda ())
Have a nice day
Tomas Volf
ever as we can see it does:
;;; (("x"))
;;; (3 1)
Have a nice day
Tomas Volf
)))
(test-skip 1)
(test-expect-fail 1)
(test-assert #t)
(test-end)
However it does not:
;;; (skip)
Have a nice day
Tomas Volf
i srfi-64))
(let ((r (test-runner-null)))
(test-runner-current r)
(test-begin "x")
(test-end "y"))
However it does not.
Have a nice day
Tomas Volf
-64/test-group-top-level.srfi64test:
8:0 0 (_)
/home/wolf/src/guile-wolfsden/tests/srfi-64/test-group-top-level.srfi64test:8:0:
In procedure struct-vtable: Wrong type argument in position 1 (expecting
struct): #f
Have a nice day
Tomas Volf
1 - 100 of 164 matches
Mail list logo
