On 6 May 2012 12:52, Ian Price wrote:
> Well, what I meant is a port that would be layered over the top of
> another. Soft ports or custom binary ports would be used to implement
> it. (Is there a reason (effiencywise) to prefer one over the other?)
>
Intuitively I would think custom binary ports
On 9 June 2012 20:32, David Kastrup wrote:
>
> Hi,
>
> the main data structure of Lua is a "table", an associative array, and a
> table t has a continguous numerically addressed part from 1..#t, with
> all other indices going through a hashing mechanism. One principal
> distinguishing feature, li
On 11 June 2012 12:37, David Kastrup wrote:
> What is a vlist?
vlist is a data type introduced around guile 2.0. You will find it
documented in the Guile Reference under Compound Data Types.
They are growable and provide vector-like access performances and
memory locality.
>>> Now it would be
On 11 June 2012 15:25, David Kastrup wrote:
> Yes, but then it will actually be quite rare that the structure is
> extended while it is read rather often. It would probably do fine to
> just do the extension lazily by exception, but then wrapping a catch
> around every access is likely to be slow
On 11 June 2012 17:01, Daniel Hartwig wrote:
> For reference, attached is a growable vector I use in several
> projects, adapted to support the length operation similar to Lua (i.e.
> first unset numerical index). There is no catching of exceptions
> here, every access to the data is
On 11 June 2012 18:38, David Kastrup wrote:
> Well, considering the cost of dynvector-grow!, doing the growth in a
> loop rather then just the determination of the new size seems a bit
> expensive:
Only if you are repeatedly setting values at indices far beyond the
current capacity. This does no
On 11 June 2012 20:00, David Kastrup wrote:
>> I guess to summarize: if you want an abstraction like tables, you would
>> build it out of vectors and hash tables. But vectors and hash tables
>> themselves are the lower-level building blocks.
>
> Not low-level enough: they are already specialized
On 11 June 2012 20:20, David Kastrup wrote:
>> P.S.: I still need to look at vlists. They might already address this
>> issue, though I can't use them in Guile 1.8.
>
> No, the "immutable" angle would make them unsuitable again.
Note that vlists are only immutable in the sense that you can
On 13 June 2012 14:55, Nala Ginrut wrote:
> hi folks! I'm on my trip and inconvenient to meet you guys on IRC.
> Things gonna be normal next month.
>
> Anyway, there's a problem for you.
> I'm trying to write a simple wrapper for "sed" with our popen module:
> --code
> (use
On 14 June 2012 22:47, David Kastrup wrote:
> Mark H Weaver writes:
>
>> David Kastrup writes:
>>> Scheme/Guile vectors are fixed size. [...] It is a bit of a nuisance
>>> that one can grow a hashtable efficiently and on-demand, but not so an
>>> array.
>>
>> Although Scheme vectors should rem
On 14 June 2012 23:34, David Kastrup wrote:
> Daniel Hartwig writes:
>> The
>> guile core provides already a solid set of fundamental types which are
>> very easy to compose to produce *exactly* the type required for any
>> particular situation.
>
> Except when t
On 15 June 2012 01:15, David Kastrup wrote:
> Daniel Hartwig writes:
>> What is this half-in-place algorithm that makes this efficient? If
>> the table is to remain balanced, all items should be rehashed and
>> reallocated to a new bucket and there is no correlation betwee
On 11 September 2012 13:38, Chris K. Jester-Young wrote:
> It's been over half a year since I last wrote about SRFI 41; two whole
> releases have happened since then. I'm pretty sure I don't want to wait
> for another. ;-)
Hello
This is not compatible with the (ice-9 streams) module is it? At
l
On 19 September 2012 03:59, Chris K. Jester-Young wrote:
> (define* (regexp-split pat str #:optional (limit 0))
> […]
> (reverse (if (zero? limit)
> (drop-while string-null? final)
> final
>
Please simplify this limit arg, removing the maybe-drop-empty-st
Following up on the thread from last time regexp-split was discussed.
On 8 January 2012 07:05, Andy Wingo wrote:
> On Sat 31 Dec 2011 06:54, Daniel Hartwig writes:
>> * [Vanilla `string-split' expanded to support the CHAR_PRED
>> semantics of `string-index' et a
Hi Mark
Thanks for the speedy response.
General ACK on all your comments. Some additional notes:
On 8 October 2012 23:40, Mark H Weaver wrote:
>> [which vs. that]
This was straight out of the doc string for string-index. Changed.
>> + if (SCM_CHARP (char_pred))
>> +{
>> + goto spl
On 10 October 2012 01:48, Mark H Weaver wrote:
>> + if (!SCM_CHARSETP (char_pred))
>> {
>> - last_idx = idx;
>> - while (idx > 0 && buf[idx-1] != SCM_CHAR(chr))
>> -idx--;
>> - if (idx >= 0)
>> -{
>> - res = scm_cons (sc
On 10 October 2012 10:14, Mark H Weaver wrote:
> Your latest patch looks good, but I just remembered one more thing:
> doc/ref/api-data.texi needs to be updated.
I had assumed that was updated automatically from the doc strings,
which are in the right format.
?
On 10 October 2012 11:25, Mark H Weaver wrote:
> Daniel Hartwig writes:
>
>> On 10 October 2012 10:14, Mark H Weaver wrote:
>>> Your latest patch looks good, but I just remembered one more thing:
>>> doc/ref/api-data.texi needs to be updated.
>>
>> I
Patch with .texi updated also.
0001-In-string-split-add-support-for-character-sets-and-p.patch
Description: Binary data
On 20 October 2012 22:16, Mark H Weaver wrote:
> Honestly, this question makes me wonder if the proposed 'regexp-split'
> is too complicated. If you want to trim whitespace, how about using
> 'string-trim-right' or 'string-trim-both' before splitting? It seems
> more likely to do what I would ex
On 7 November 2012 21:46, Mark H Weaver wrote:
> Here's an improved version the patch that gracefully handles the case
> where creation of the worker pool is unsuccessful due to an exception or
> cancelled thread.
>
> What do you think?
Looks clean. Nice work picking up on this race condition.
On 20 November 2012 08:24, Ian Price wrote:
> I'm no expert on lua, so I can't give you a huge long list, but Phil did
> make a post titled "Creating a Lua Roadmap" at
> http://article.gmane.org/gmane.lisp.guile.devel/12291
>
> The first issues would be them. There appears to be a notes.org in the
On 29 November 2012 06:00, Ludovic Courtès wrote:
> Hi,
>
> I just added two web client procedures: ‘response-body-port’ and
> ‘http-get*’, both of which return an input port from which to read a
> response’s body.
Hi
This is a very useful and tidily done addition. Makes sense, diff
looks ok, a
On 2 December 2012 00:31, nalaginrut wrote:
> I think a colorized REPL is useful for our users.
> Will you accept a patch to 'pp' for colorized REPL? Or an easy way, a
> module with hook to do the same job, but output twice?
Perhaps rather implement this as a separate, “advanced” interface.
Think
On 4 December 2012 13:19, nalaginrut wrote:
> Hi Daniel!
> I believe this patch simplified my work, and 'colorized' module has been
> finished, I'm testing and debugging.
> I'll post it when it's all done.
Glad to hear it.
Attached is an alternate patch that handles before-print-hook and
*unspec
On 4 December 2012 14:30, nalaginrut wrote:
> And I'll update it to repl-option version after ludo/andy accepts your
> patch.
>
> Or I should post it include your patch altogether? ;-)
Separate is easier to work with.
On 4 December 2012 14:39, Thien-Thi Nguyen wrote:
> () Daniel Hartwig
> () Tue, 4 Dec 2012 13:34:52 +0800
>
>patch that handles [...] *unspecified*
>
> Can ‘unspecified?’ (the procedure) be used? I seem to recall people
> wanting to avoid using ‘*unspecified*’ (the u
On 5 December 2012 15:21, Nala Ginrut wrote:
> Hi folks!
> Here's a patch to add colorized-REPL.
Some comments :-)
diff --git a/module/ice-9/colorized.scm b/module/ice-9/colorized.scm
new file mode 100644
index 000..fe42a9a
--- /dev/null
+++ b/module/ice-9/colorized.scm
@@ -0,0 +1,290 @@
+;;
On 5 December 2012 16:48, Nala Ginrut wrote:
>> Is there some advantage to using the GOOPS classes rather than
>> equivalent predicates, which are more universal? Of course, the order
>> of the tests matters highly in both cases.
>>
>
> GOOPS classes covered all the possible types in Guile, and i
On 5 December 2012 17:50, Daniel Llorens wrote:
> I think that (os process) should be merged in Guile in some
> form, run-with-pipe has appeared in the lists a few times.
Yes, this was ACK during one of those discussions.
I believe most of the problem with open-pipe may have been resolved by
ch
On 5 December 2012 18:27, Nala Ginrut wrote:
> I can understand this too. So your suggestion is to write a
> (term ansi-color) compatible interface. I think it's easy to do.
> But I'm afraid that Guile don't integrate (term ansi-color).
In your code, one uses "(light-blue yellow)", and only some
On 6 December 2012 10:43, Nala Ginrut wrote:
> But if we need the original author to assign the copyright, I'm not sure
> how long will it be. Last time I assigned the copyright took about one
> month, since it's long way to send a hand-written assignment to USA.
> Or I just request the original a
On 6 December 2012 12:28, Nala Ginrut wrote:
> I was aimed to patch pretty-print for coloring. But I changed my mind
> because an independent module is easy to develop and debug.
Yes, I thought as much. Do keep the eventual integration in mind,
since I'm sure the maintainers are not interested i
On 9 December 2012 05:35, Ian Price wrote:
> Or, you could use the package manager I keep pimping :)
Yes indeed, it works quite well. As does just adding such files to a
site- or user-local module path.
> (os process) might be reasonable, since we are forever complaining about
> the popen modul
On 12 December 2012 11:21, Nala Ginrut wrote:
> It's weird to see that:
> (exact? 'a)
> err msg===
> ERROR: In procedure exact?:
> ERROR: In procedure exact?: Wrong type argument in position 1: a
> ==end=
>
> And I have to do this:
> (def
[No need to Cc the bug report]
On 12 December 2012 12:03, Nala Ginrut wrote:
> Seems (fluid-ref *repl-stack*) is not a pair/list when REPL is just
> started?
Correction: is not a pair/list when /guile/ is just started. The
program, guile, is not a REPL, that is only an optional component of
it.
On 12 December 2012 14:01, Daniel Hartwig wrote:
> On 12 December 2012 13:49, Nala Ginrut wrote:
>> repl-default-option-set! seems didn't make sense.
>
> Works fine for me.
>
>>
>> I believe people more like to activate the colored-REPL automatically
>>
On 12 December 2012 13:55, Nala Ginrut wrote:
> Are you suggesting I use (is-a? obj ) for 'fraction?' ?
Absolutely not. Use inexact? if you wish to determine that the
*storage* of a value is using floating point format.
On 12 December 2012 14:32, Mark H Weaver wrote:
> Daniel Hartwig writes:
>> On 12 December 2012 13:55, Nala Ginrut wrote:
>>> Are you suggesting I use (is-a? obj ) for 'fraction?' ?
>>
>> Absolutely not. Use inexact? if you wish to determine that the
&
Hello again
Some comments in addition to Ludo's below. I have not inspected the
code of your latest submission thoroughly, but enough to agree that
there are many stylistic and algorithmic issues. I will probably not
be looking in to it any more, and remain a satisfied user of
emacs+geiser.
I s
On 11 January 2013 14:29, Nala Ginrut wrote:
> On Thu, 2013-01-10 at 16:19 +0800, Daniel Hartwig wrote:
> I changed these:
> string-in-color => colorize-string
> display-string-in-color => colorized-display
>
> What do you think?
Nicer anway.
>> Also, the “/” i
On 11 January 2013 22:33, Ludovic Courtès wrote:
>>> > +(define *color-list*
>>> > + `((CLEAR . "0")
>>> > +(RESET . "0")
>>> > +(BOLD. "1")
>>> > +(DARK. "2")
>>> Would it make sense to define a new type for colors? Like:
>>>
>>> (define-record
On 11 January 2013 18:40, Nala Ginrut wrote:
> Yes, that's a good point, and the test case could move out of the module
> itself.
It should.
>> I suppose the original comments were not so clear. It is not only the
>> string but other members such as “data” that do not fit the concept of
>> “col
On 12 January 2013 02:49, Andy Wingo wrote:
>> ‘http-get*’ was added in 2.0.7, so it doesn’t seem wise to deprecate it
>> just a couple of months later, no?
>
> In many ways it's better to deprecate early while there are few users,
> and the change was recent. It's not like the interfaces are act
5 (open-input-string (make-string 60 #\0)))
$1 = "5b19445b70b493c78f3bc06eb7962315"
Regards
>From 47c92db862ce846dbcc5d27843bc9d26b7708d5d Mon Sep 17 00:00:00 2001
From: Daniel Hartwig
Date: Sat, 12 Jan 2013 14:34:26 +0800
Subject: [PATCH] md5: fix errors when input size modulo 64 is >
On 12 January 2013 14:43, Daniel Hartwig wrote:
>
> Originally reported as <http://bugs.debian.org/437214>.
>
> Triggered when input has size modulo 64 is 56–63 bytes.
>
> scheme@(guile-user)> (use-modules (md5))
… from guile-lib, of course!
On 12 January 2013 16:35, Nala Ginrut wrote:
> I suggest add a 'digest' module implemented in C code in Guile to
> provide common see 'digest algorithm', since these things are very
> useful nowadays. I believe they should be in ice-9. Like Ruby does.
> I've started a project guile-digest. I'll se
On 31 January 2013 13:31, Daniel Hartwig wrote:
> On 22 January 2013 05:16, Andy Wingo wrote:
>> Any chance on getting a test case as well? :-)
>> --
>> http://wingolog.org/
>
> Updated with tests from RFC 1321. Confirmed that the new test fails
> pre-patch.
Ple
On 22 January 2013 05:16, Andy Wingo wrote:
> Any chance on getting a test case as well? :-)
> --
> http://wingolog.org/
Updated with tests from RFC 1321. Confirmed that the new test fails pre-patch.
0001-md5-fix-errors-when-input-size-modulo-64-is-55-bytes.patch
Description: Binary data
* libguile/gen-scmconfig.c: Determine the size of ssize_t (POSIX).
* libguile/foreign.c: New symbol is an alias for a signed integer type.
* module/system/foreign.scm: Export the new symbol.
* doc/ref/api-foreign.texi (Foreign Types): Document.
---
doc/ref/api-foreign.texi |1 +
libguile/f
Hello
On 3 February 2013 20:55, Nala Ginrut wrote:
> As mentioned in another thread about digest algorithm support in Guile,
> my plan is use part of implementation of libgcrypt and make a wrapper,
> then put into libguile.
> But now I found weinholt's Scheme industria lib, which contains all
> m
On 31 January 2013 18:23, Andy Wingo wrote:
> Guile-Lib is intended as an accumulation place for pure-scheme Guile
> modules, allowing for people to cooperate integrating their generic
> Guile modules into a coherent library. Think "a down-scaled,
> limited-scope CPAN for Guile".
Is guile-lib int
On 4 February 2013 11:12, Nala Ginrut wrote:
>> If your goal is only to provide crypto. support to Guile programs,
>> then time is better spent providing a wrapper to the existing library.
>> Concerns about adding an external dependency do not hold much weight
>> next to the advantages of directl
On 4 February 2013 18:58, Andy Wingo wrote:
> On Mon 04 Feb 2013 03:07, Daniel Hartwig writes:
>> Is guile-lib interested in receiving new code?
>
> Dunno! I'm not sure. Now that we have the guildhall starting up, I
> would be inclined to say "no". Better a d
On 5 February 2013 23:48, Ludovic Courtès wrote:
>> The gcrypt-guile project is doing so, I'll help it if I can.
>> But my original thought is orthogonal with gcrypt-guile, just put some
>> common digest algorithm in libguile rather than a full-stack crypto-lib.
>
> We could actually use the Gnuli
On 6 February 2013 12:18, Daniel Hartwig wrote:
> Avoiding duplication and feature creep /in the core/ is highly
> desirable. Guildhall makes it convenient enough to pull in additional
> features; guile-lib has md5 and industria provides also sha and
> others.
During yesterday'
On 9 February 2013 00:21, Ludovic Courtès wrote:
>
> Yeah, apparently there are several half-baked bindings around. Let’s
> just polish one of them, and submit it for inclusion in libgcrypt.
I have already submitted some additions to one, but I may just continue
in a new repository.
By the way,
On 6 February 2013 21:13, Nala Ginrut wrote:
> /usr/share/mime is contained in 'shared-mime-info' package, at least for
> openSUSE. The suggestion you gave means Guile will depend on this
> package. Personally, I don't think that's what you want. ;-P
Hi
The suggestion was to support reading the
On 11 February 2013 17:38, Nala Ginrut wrote:
> But there's a different for MIME, since it should be a part of web
> module IMO (or not?). So I'm hesitated again.
There is no pressing need to include or not. While it is a work in
progress it is easier to distribute and inspect if it is an extern
On 11 February 2013 23:23, Greg Troxel wrote:
> (First, "all mainstream distros" is only talking about Linux.)
>
> This .so=>devel does not make sense to me. I thought the point was
> that -devel split things that people who wanted to compile against the
> package needed, but not things needed t
On 12 February 2013 12:20, Nala Ginrut wrote:
> Put that link .so in guile rather than guile-devel is the exception I
> mentioned. The regular packaging policy not allow it.
>
[Again, referring only to Debian.]
Right. This applies only to libguilereadline-v-18.so, not
libguile-2.0.so. I had ov
* doc/ref/api-foreign.texi (Foreign Types): Replace references to the
old foreign->bytevector and bytevector->foreign with the new procedure
names using pointer.
---
doc/ref/api-foreign.texi |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ref/api-foreign.texi b/d
On 17 February 2013 13:03, Nala Ginrut wrote:
> PS: and I have to mention that bug, I believe it's a bug.
>
> When the server-handler get the request, I found the uri in request have
> no 'host', it's #f. It causes trouble for me to implement url redirect
> mechanism, which used to implement admin
On 17 February 2013 13:03, Nala Ginrut wrote:
> I put here:
> https://gitorious.org/glow/artanis
The examples you mentioned make this look very interested. Nice job.
On 19 February 2013 00:25, Mike Gran wrote:
> From: Noah Lavine
>>Hello,
>>>On Wed 23 Jan 2013 13:20, Daniel Llorens writes:
>>>
In [2]: a = np.array([[1, 2, 3], [4, 5, 6], [7, 8, 9]])
>>>
In [4]: a[1]
Out[4]: array([4, 5, 6])
In [5]: a[1, 1]
Out[5]: 5
array-re
Hi
It seems you are expecting some CLOS behaviour in a language that can
not support it. The accessors are generic functions, but each of your
modules creates a unique generic function, there is no implicit
namespace sharing in Scheme. Define a base module with an appropriate
superclass or inter
On 23 February 2013 07:11, David Pirotte wrote:
> Hi Daniel,
>
> thanks for your answer, but where i understand a strict name space will lead
> to
> merging the generic(s) from/with the ones that comes from the modules you are
> importing [as opposed to a general 'goops' name space], i disagree t
On 22 February 2013 04:59, wrote:
> I also suggest that for people writing compatability code that we have
> a standard namespace for this. Let me suggest
>
> (compat name-of-scheme/lisp component ...)
> e.g.
> (compat racket match)
> (compat racket for)
> (compat racket struct)
>
> The idea is t
On 24 February 2013 18:45, Mark H Weaver wrote:
> Hi Daniel,
>
> Daniel Hartwig writes:
>> * Terminology
>>
>> The terminology used in latest URI spec. (RFC 3986) is not widely used
>> elsewhere. Not by Guile, not by the HTTP spec., or other sources.
>&g
On 3 March 2013 03:36, Andy Wingo wrote:
> Hi Bake,
>
> On Fri 03 Feb 2012 14:28, Andy Wingo writes:
>
>> Hi Bake,
>>
>> This patch looks great. I do have a couple of comments before
>> applying. It would probably be useful to have input from others as
>> well, so I'm copying guile-devel.
>>
>>
On 6 March 2013 05:14, Mark H Weaver wrote:
> * [Daniel Hartwig?] Support Relative URIs in (web uri)
Although I have been unexpectedly busy this week, I will certainly be
able to complete this task shortly.
Regards
On 3 March 2013 17:45, Andy Wingo wrote:
> On Sun 03 Mar 2013 02:07, Daniel Hartwig writes:
>
>> Can I ask whether it is preferred to use, e.g. @code{#f}, for the
>> default values, as some places seem to and others don't. This patch
>> is not using @code, but th
On 9 March 2013 09:58, Daniel Hartwig wrote:
> On 3 March 2013 17:45, Andy Wingo wrote:
>> On Sun 03 Mar 2013 02:07, Daniel Hartwig writes:
>>
>>> Can I ask whether it is preferred to use, e.g. @code{#f}, for the
>>> default values, as some places seem to and
On 9 March 2013 16:25, Andy Wingo wrote:
> Should we remove the brackets entirely? i.e
I would not. The brackets are fairly standard for optional arguments.
> ** New `print' REPL option.
>
> See "REPL Commands" in the manual for information on the new
> user-customizable REPL printer.
Since adding this option I have noticed that reader is also
customizable, using the undocumented variable ‘repl-reader’. The
interface here is different. A custom prin
On 23 March 2013 06:33, Stefan Israelsson Tampe wrote:
> (define (f x)
> (let ((s 0))
> (with-special-soft ((s 0))
>(let lp ((i 0))
> (cond
> ((>= i 100) s)
> ((= i 50) (abort-to-prompt 'tag) (lp (+ i 1)))
> (else (set! s (+ s i)) (lp
On 23 March 2013 19:18, Brent Pinkney wrote:
> Hi,
>
> I desperately need to write a generic method that binds to a hash-table.
>
> I have noticed that native scheme types like pair, list, and vector are
> automagically recognised in GOOPS as , , and .
> Even SRFI-19 dates are recognised as .
How
On 23 March 2013 23:15, Brent Pinkney wrote:
> On 23/03/2013 16:09, Daniel Hartwig wrote:
>>
>> On 23 March 2013 19:18, Brent Pinkney wrote:
>>>
>>> Hi,
>>>
>>> I desperately need to write a generic method that binds to a hash-table.
>&g
On 23 March 2013 23:19, Daniel Hartwig wrote:
> On 23 March 2013 23:15, Brent Pinkney wrote:
>> Ok, so you have confirmed that you can merrily make my enumerate! method ?
>>
>> I still fail to.
>
> Which hash tables are you using?
>
> scheme@(guile-user)> (
On 27 March 2013 08:47, Nala Ginrut wrote:
>
> 在 2013-3-27 AM5:59，"Ludovic Courtès" 写道：
>
>
>>
>> Nala Ginrut skribis:
>>
Hi now
>> > * hash-items: get the amount of items in the hash table
>>
>> There’s already ‘hash-count’, recently added.
>>
>
> If I need to check the amount of items
> each
On 27 March 2013 14:32, Nala Ginrut wrote:
> On Wed, 2013-03-27 at 13:10 +0800, Daniel Hartwig wrote:
>> On 27 March 2013 08:47, Nala Ginrut wrote:
>> >
>> > 在 2013-3-27 AM5:59，"Ludovic Courtès" 写道：
>> >
>> >
>> >>
>> >
On 31 March 2013 05:17, Mark H Weaver wrote:
> Nala Ginrut writes:
>> +
>> +(define (print-src p)
>> + (define (get-program-src p)
>> +(let ((source (program-source p 0)))
>> + (cond
>> + ((not source) "It's inner procedure implemented with C")
>
> I'm not sure we can conclude tha
On 31 March 2013 20:47, Nala Ginrut wrote:
> On Sat, 2013-03-30 at 17:17 -0400, Mark H Weaver wrote:
>> This strategy of reading the code is not robust.
>>
>> * It assumes that the procedure is the first datum on the specified
>> line. This is not generally true.
>
> Yes, I saw that. But I don'
On 1 April 2013 05:16, Stefan Israelsson Tampe wrote:
> Note two things
> * it's better to pile up the redo-safe-variables with a parameter
> then the clumsy version in the previous mail which will not work well.
>
> * A continuation that backtracks from down the stack back to the creation of
> t
On 1 April 2013 11:54, Mark H Weaver wrote:
> Daniel Hartwig writes:
>> these two points are enough information to obtain the unmodified
>> source from the file.
>
> This is enough to get the original characters, but then there's the
> other problem I mentioned: read
2013/4/1 Nala Ginrut :
> I've tried to implement a function to mimic string multiply like Python:
> "asdf" * 10
>
> --code
> (define (str* str n)
> (format #f "~{~a~}" (make-list n str)))
>
> or
>
> (define (str* str n)
> (string-join (make-list n str) ""))
> ---
2013/4/1 Nala Ginrut :
> Anyway, string-join is so slowly beyond my expectation.
Also note that ‘string-concatenate’ (less general than ‘string-join’)
performs better for the same case, you could use that directly instead
of my prior suggestion for similar results. Especially since you do
not des
On 1 April 2013 14:58, Nala Ginrut wrote:
> On Mon, 2013-04-01 at 13:35 +0800, Daniel Hartwig wrote:
>> 2013/4/1 Nala Ginrut :
>> > Anyway, string-join is so slowly beyond my expectation.
>>
>> Also note that ‘string-concatenate’ (less general than ‘string-join’)
&
On 1 April 2013 14:59, Daniel Llorens wrote:
>
> Hello,
>
>> From: Daniel Hartwig
>>
>> (define (str* str n)
>> (call-with-output-string
>>(lambda (p)
>> (let lp ((n n))
>>(unless (zero? n)
>> (display str p)
On 4 April 2013 12:39, Nala Ginrut wrote:
> I don't think it's necessary to add the docs since it's explicit.
> It may help for some guys like me. ;-)
Every part of the API must be documented. How else do guys like you
know this is there?
On 4 April 2013 12:39, Nala Ginrut wrote:
> Here's a patch to add backlog option to http-open, users may use it
> like:
>
> ---cut
> (run-server (lambda (r b) ...)
> 'http
> '(#:port 1234 #:backlog 1024))
> ---
On 6 April 2013 12:14, Nala Ginrut wrote:
> Resend patch, added the example for #:backlog.
> Since there's no docs for all run-server open-params, but examples.
> So I just added the example. I think it's enough to explain the usage.
You missed to add it to the preceding ‘@deffn’.
I don't think
On 8 April 2013 00:49, Chris K. Jester-Young wrote:
> Hi all,
>
> I've attached record type printers for SRFI 45 promises and SRFI 41
> streams. I've tried to make promise-visit more self-documenting with
> the use of keyword arguments; let me know if you think that's an
> improvement!
>
> Also as
On 8 April 2013 07:13, Daniel Hartwig wrote:
> On 8 April 2013 00:49, Chris K. Jester-Young wrote:
>> Hi all,
>>
>> I've attached record type printers for SRFI 45 promises and SRFI 41
>> streams. I've tried to make promise-visit more self-documenting with
&g
On 11 April 2013 07:07, Daniel Llorens wrote:
>
> After the array-map patches, I've gone through the vector/array
> implementation and there's some stuff I'd like to fix. In stable-2.0 today:
>
> (define a (make-typed-array ''f64 0 '(1 2))
> a
> => #1f64@1(0.0 0.0)
>
> so far so good.
>
> (unifor
On 11 April 2013 13:37, Ian Price wrote:
>
>> So, what do you think?
>
> This is the sort of thing that belongs in a .guile rather than in
> guile IMO.
>
Right, and since you can already do this with more control via the
posix interface, adding this 'shortcut' to the repl adds little in the
way o
On 12 April 2013 14:29, Nala Ginrut wrote:
> On Fri, 2013-04-12 at 07:55 +0800, Daniel Hartwig wrote:
>> On 11 April 2013 13:37, Ian Price wrote:
>> >
>> >> So, what do you think?
>> >
>> > This is the sort of thing that belongs in a .guile rath
On 12 April 2013 15:23, Daniel Llorens wrote:
>
> Right. I want [0]
>
> (vector-ref #@1(1 2 3 4) 1) => 2
>
> to fail with a type error, which is consistent with r5rs.
>
Ah. I should have read more the later part of your mail.
> However my proposal is also to produce the same type error when
> t
On 12 April 2013 18:15, Daniel Hartwig wrote:
> From your original mail:
>> a. the array implementation can rely on all [vector] types
>> having known base=0 and inc=1.
>
> Is that not already the case?
>
Ah right, not when ‘vector?’ answers #t to compatible arrays.
1 - 100 of 140 matches
Mail list logo
