From: Brian Rogoff <bpr@best.com>
To: caml-list@inria.fr
Subject: Array interface question
Date: Fri, 22 Jan 1999 11:10:40 -0800 (PST) [thread overview]
Message-ID: <Pine.BSF.4.05.9901221056370.3130-100000@shell5.ba.best.com> (raw)
Hi,
Why is there no creation function which does not take a default
value for filling the array? When building abstractions like dynamic
arrays or (SRC Modula-3 style) Sequences on top of Arrays I'm forced to
provide a fill value even though the abstraction really doesn't call for
one. Is this a simple omission, or is there some compelling reason for
leaving this out?
-- Brian
next reply other threads:[~1999-01-22 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-22 19:10 Brian Rogoff [this message]
1999-01-22 19:21 ` Pierre Weis
1999-01-22 20:05 ` Brian Rogoff
1999-01-23 10:47 ` Anton Moscal
1999-01-23 10:57 ` David Monniaux
1999-01-24 15:44 ` Jerome Vouillon
1999-01-24 21:36 ` Pierre Weis
1999-01-28 19:57 ` Brian Rogoff
1999-01-23 14:00 ` Size of arrays Juan Jose Garcia Ripoll
1999-01-24 22:31 ` Pierre Weis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.4.05.9901221056370.3130-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).