This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.
Source for ticket #85
cc
changetime
2012-08-27 06:56:47
component
WG1 - Core
description
Now that we have blobs, we have to decide what to call them.
id
85
keywords
milestone
owner
alexshinn
priority
major
reporter
cowan
resolution
fixed
severity
status
closed
summary
Blobs, bytevectors, byte-vectors, octet-vectors, or something else?
time
2010-10-18 03:20:08
type
defect
Changes
Change at time 2012-08-27 06:56:47
author
cowan
field
comment
newvalue
oldvalue
9
raw-time
1346025407533372
ticket
85
time
2012-08-27 06:56:47
Change at time 2012-08-27 06:56:47
author
cowan
field
resolution
newvalue
fixed
oldvalue
raw-time
1346025407533372
ticket
85
time
2012-08-27 06:56:47
Change at time 2012-08-27 06:56:47
author
cowan
field
status
newvalue
closed
oldvalue
decided
raw-time
1346025407533372
ticket
85
time
2012-08-27 06:56:47
Change at time 2012-08-25 00:30:54
author
cowan
field
comment
newvalue
WG1 decided to keep the name `bytevector`.
oldvalue
8
raw-time
1345829454688329
ticket
85
time
2012-08-25 00:30:54
Change at time 2012-08-25 00:30:54
author
cowan
field
status
newvalue
decided
oldvalue
reopened
raw-time
1345829454688329
ticket
85
time
2012-08-25 00:30:54
Change at time 2012-07-15 01:16:44
author
cowan
field
comment
newvalue
oldvalue
7
raw-time
1342289804111953
ticket
85
time
2012-07-15 01:16:44
Change at time 2012-07-15 01:16:44
author
cowan
field
resolution
newvalue
oldvalue
fixed
raw-time
1342289804111953
ticket
85
time
2012-07-15 01:16:44
Change at time 2012-07-15 01:16:44
author
cowan
field
status
newvalue
reopened
oldvalue
closed
raw-time
1342289804111953
ticket
85
time
2012-07-15 01:16:44
Change at time 2012-07-15 01:16:34
author
cowan
field
comment
newvalue
Reopened due to public comments.
oldvalue
6
raw-time
1342289794902795
ticket
85
time
2012-07-15 01:16:34
Change at time 2012-07-15 01:16:34
author
cowan
field
resolution
newvalue
fixed
oldvalue
raw-time
1342289794902795
ticket
85
time
2012-07-15 01:16:34
Change at time 2012-07-15 01:16:34
author
cowan
field
status
newvalue
closed
oldvalue
writing
raw-time
1342289794902795
ticket
85
time
2012-07-15 01:16:34
Change at time 2011-07-10 20:25:39
author
alexshinn
field
comment
newvalue
oldvalue
5
raw-time
1310304339000000
ticket
85
time
2011-07-10 20:25:39
Change at time 2011-07-10 20:25:39
author
alexshinn
field
status
newvalue
writing
oldvalue
decided
raw-time
1310304339000000
ticket
85
time
2011-07-10 20:25:39
Change at time 2011-07-10 17:54:06
author
alexshinn
field
comment
newvalue
We voted to use the R6RS term `bytevector`.
oldvalue
4
raw-time
1310295246000000
ticket
85
time
2011-07-10 17:54:06
Change at time 2011-07-10 17:54:06
author
alexshinn
field
resolution
newvalue
oldvalue
raw-time
1310295246000000
ticket
85
time
2011-07-10 17:54:06
Change at time 2011-07-10 17:54:06
author
alexshinn
field
status
newvalue
decided
oldvalue
new
raw-time
1310295246000000
ticket
85
time
2011-07-10 17:54:06
Change at time 2010-10-20 06:10:48
author
arcfide
field
comment
newvalue
Blob doesn't really mean anything though, which is why I don't like it. It doesn't give you any suggestions about how you might interact with it, when in actuality, we are enforcing a certain basic idea: a vector of bytes. Whether we extract those bytes out and use them in various different ways doesn't detract from this. Blob just kind of sounds ugly to me, as well. A vector of bytes implies what I want in the interface, namely that you reference elements in that vector by byte offset, that you treat it like a contiguous set of bytes, and so forth. Blob could mean anything to me, and I have no intuition about its interface. u8vector is okay, as is byte-vector and vector-b8, but each of those is, IMO, less convenient or more obtuse than bytevector.
oldvalue
3
raw-time
1287529848000000
ticket
85
time
2010-10-20 06:10:48
Change at time 2010-10-19 23:37:53
author
cowan
field
comment
newvalue
Outside R6RS, the most common name is ''u8vector'', tracking SRFI 4. However, ''byte-vector'', ''vector-b8'', ''blob'', and other names are also in use.
I favor ''blob'' myself, because blobs can be analyzed in any number of ways, not just as vectors of bytes.
oldvalue
2
raw-time
1287506273000000
ticket
85
time
2010-10-19 23:37:53
Change at time 2010-10-19 03:39:29
author
arcfide
field
comment
newvalue
I think that we should go with bytevectors, which is a fairly clear name, has precedent and is in widespread common use.
oldvalue
1
raw-time
1287434369000000
ticket
85
time
2010-10-19 03:39:29