From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Subject: max-iterations in ice-9/format.scm
Date: Sat, 8 Mar 2003 04:11:19 -0800 [thread overview]
Message-ID: <200303081211.EAA12227@cmn14.stanford.edu> (raw)
Currently format truncates a list at the 100th item without any warning:
(define nums (list
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115
116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145
146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174
175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199))
(format #f "~{~A ~}" nums)
"0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 "
This is because line 618 sets "max-iterations" to 100 if it isn't
otherwise prescribed. Here is a diff that fixes it:
/home/bil/cl/ diff format.scm ../test/guile-1.6.2/ice-9/format.scm
618,619c618
< ;(else (if (not max-iterations) (set! max-iterations 100)))
< )
---
> (else (if (not max-iterations) (set! max-iterations 100))))
641c640
< (and max-iterations (>= i max-iterations)))))))
---
> (>= i max-iterations))))))
650c649
< (and max-iterations (>= arg-pos max-iterations))))
---
> (>= arg-pos max-iterations)))
667c666
< (and max-iterations (>= i max-iterations)))
---
> (>= i max-iterations))
676c675
< (and max-iterations (>= arg-pos max-iterations)))
---
> (>= arg-pos max-iterations))
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
reply other threads:[~2003-03-08 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303081211.EAA12227@cmn14.stanford.edu \
--to=bil@ccrma.stanford.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).