Email list hosting service & mailing list manager

list*->array argument order Bradley Lucier (20 Feb 2022 17:55 UTC)
Re: list*->array argument order Arthur A. Gleckler (21 Feb 2022 02:32 UTC)
Re: list*->array argument order Lucier, Bradley J (21 Feb 2022 13:40 UTC)
Re: list*->array argument order Bradley Lucier (21 Feb 2022 21:44 UTC)
Re: list*->array argument order Bradley Lucier (03 Mar 2022 19:53 UTC)
Re: list*->array argument order Jens Axel Søgaard (21 Feb 2022 21:45 UTC)

Re: list*->array argument order Bradley Lucier 21 Feb 2022 21:44 UTC

On 2/20/22 9:31 PM, Arthur A. Gleckler wrote:
> On Sun, Feb 20, 2022 at 12:55 PM Bradley Lucier <xxxxxx@math.purdue.edu
> <mailto:xxxxxx@math.purdue.edu>> wrote:
>
>     The first two arguments are required, but I'm beginning to think that
>     the short required argument, the dimension, should come before the data
>     itself, which can be quite large.
>
>
> [Editor's hat off.]  That sounds smart to me.  Most of the time, the
> data won't be literal, but sometimes it is, and I don't see any reason
> to choose the other order.

Thinking about it again, because a list/vector/list*/vector* is being
converted to an array, with some auxiliary information, maybe it is a
good idea to have an argument-list convention of

(define (list->array    list    domain-interval ...))
(define (list*->array   list*   dimension ...))
(define (vector->array  vector  domain-interval ...))
(define (vector*->array vector* dimension ...))

Brad