Naming of Array support functions (remaining: IsArrayBegin IsArrayEnd) about oscpack

[GoogleCodeExporter]

naming: the osc1.0 specs talk about `begin` and `end` (array boundaries are 
optional type tags). so it would be reasonable to use that. adding `Marker` ... 
not sure if it increases the expressive power of the API, but i'm not a native 
speaker

computing element count: probably a good idea to add `Compute' to the name.

Original comment by [email protected] on 4 Mar 2013 at 9:59

[GoogleCodeExporter]

I've updated SVN as follows:
ARRAY_BEGIN_TYPE_TAG, ARRAY_END_TYPE_TAG
IsArrayBegin(), IsArrayEnd()
ComputeArrayItemCount()

As a native speaker I'm not entirely happy with IsArrayBegin/End but it's an 
improvement. I'm going to sleep on it.

Original comment by ross.bencina on 4 Mar 2013 at 10:23

[GoogleCodeExporter]

I'm still struggling :

For now we have IsArrayBegin, IsArrayEnd for now. These have the advantage of 
starting with IsArray...  and ArrayBegin seems more like a noun for Is than 
BeginArray.

Some alternatives:

IsBeginArray -- Pro: BeginArray used elsewhere, Con: doesn't start with Array
IsBeginningOfArray -- Pro: reads well, in line with wording of spec, Con: 
semantics unclear (it's a pseudo argument that marks the beginning of an array, 
not actually the beginning of an array)
IsBeginningOfArrayTag -- ambiguous
IsBeginArrayMarker -- OK
IsBeginArrayTag -- OK but we don't use Tag anywhere else but it's a type tag

Original comment by ross.bencina on 6 Mar 2013 at 7:16

[GoogleCodeExporter]

Original comment by ross.bencina on 6 Mar 2013 at 7:17

• Changed title: Naming of Array support functions (remaining: IsArrayBegin IsArrayEnd)

[GoogleCodeExporter]

Closing. What we have is good enough.

Original comment by ross.bencina on 26 Mar 2013 at 9:37

• Changed state: Fixed