Some thoughts...
David Rush
(21 Nov 2001 19:26 UTC)
|
Bad things Re: Some thoughts...
Jussi Piitulainen
(21 Nov 2001 20:25 UTC)
|
Re: Bad things Re: Some thoughts...
David Rush
(22 Nov 2001 16:10 UTC)
|
Access time of elements Re: Bad things []
Jussi Piitulainen
(27 Nov 2001 10:59 UTC)
|
Re: Access time of elements Re: Bad things []
Per Bothner
(27 Nov 2001 17:10 UTC)
|
Re: Access time of elements Re: Bad things []
David Rush
(27 Nov 2001 17:25 UTC)
|
Re: Access time of elements Re: Bad things [] Per Bothner (27 Nov 2001 17:55 UTC)
|
Re: Access time of elements Re: Bad things []
David Rush
(27 Nov 2001 21:19 UTC)
|
Re: Access time of elements Re: Bad things []
Jussi Piitulainen
(28 Nov 2001 15:40 UTC)
|
Re: Access time of elements Re: Bad things []
Jussi Piitulainen
(28 Nov 2001 16:20 UTC)
|
Re: Access time of elements Re: Bad things []
Noel Welsh
(28 Nov 2001 10:55 UTC)
|
Re: Access time of elements Re: Bad things []
Jussi Piitulainen
(28 Nov 2001 17:21 UTC)
|
David Rush wrote: >Per Bothner <xxxxxx@bothner.com> writes: > >>A modest but not order-or-magnitude difference on a non-optimizing >>implementation is not does not IMO justify a less natural api. >> --Per Bothner >> >I would contend that is it a *more* natural API. I find it just as >annoying as the compiler finds it inefficient to scan past an unknown >number of arguments to find something that should *always* be there. > Of your two suggestions: 1 (array-set! a val dim0 dim1 ... dimn) 2 (array-set! a (array-index dim0 dim1 ... dimn) val) I can see some appeal in (2), but I do dislike (1). The main problem with (2) is that it adds a new concept - an "index object" data-type. --Per Bothner