Survey: What should an immutable byte sequence data structure be named?
Hey everyone, To gather more data about what the community thinks an immutable byte sequence data structure should be called (given that "string" has already been taken), I have created the following poll: https://catalyst.uw.edu/webq/survey/gcross/123312 If you have an opinion on the matter, please consider visiting the above link and submitting your favorite name. Some names that have been tossed around are istring, immutable_string, chain, rope, yarn, twine, cord, but don't feel limited to these choices. Cheers, Gregory Crosswhite
At Fri, 28 Jan 2011 12:50:25 -0800, Gregory Crosswhite wrote:
Hey everyone,
To gather more data about what the community thinks an immutable byte sequence data structure should be called (given that "string" has already been taken), I have created the following poll:
https://catalyst.uw.edu/webq/survey/gcross/123312
If you have an opinion on the matter, please consider visiting the above link and submitting your favorite name.
Some names that have been tossed around are istring, immutable_string, chain, rope, yarn, twine, cord, but don't feel limited to these choices.
Heh. "Byte sequence" already takes it out of the realm of "string" as far as I'm concerned... sounds like "buffer"... and "immutable" has several possible interpretations. Dean is talking about allowing assignability. That probably ought to be noted on the web page. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On Fri, Jan 28, 2011 at 9:50 PM, Gregory Crosswhite <gcross@phys.washington.edu> wrote:
Hey everyone,
To gather more data about what the community thinks an immutable byte sequence data structure should be called (given that "string" has already been taken), I have created the following poll:
Cool, but is there a way to see the standings (yet)? Matus
On 1/28/11 1:23 PM, Matus Chochlik wrote:
Cool, but is there a way to see the standings (yet)?
Matus
Unfortunately using this system I don't think that there is a way to create a link to the current standings, though the current standings are shown after you vote. So far the breakdown is as follows: yarn: 1 strand: 1 string: 2 chain: 5 whole_buffer: 1 immutable::string: 1 boost::text: 1 atomic_buffer: 1 const_buf: 1 tier: 1 data_block: 1 rope: 1 TOTAL: 17 Cheers, Gregory Crosswhite
From: Gregory Crosswhite Unfortunately using this system I don't think that there is a way to create a link to the current standings, though the current standings are shown after you vote.
Then it seems not to work, at least for me they weren't shown after voting. Best regards, RK
From: Gregory Crosswhite <gcross@phys.washington.edu> Hey everyone,
To gather more data about what the community thinks an immutable byte sequence data structure should be called (given that "string" has already been taken), I have created the following poll:
https://catalyst.uw.edu/webq/survey/gcross/123312
If you have an opinion on the matter, please consider visiting the above link and submitting your favorite name.
This link declines by browser... !$#$%^$%@#%$ (And this is Iceweasel 3 = Firefox 3 on Linux!) Fix it or don't use services that decline it So I put it there: boost::text Rationale same as ICU that has UnicodeString for real continuous mutable string and Text for text chunks.
On Fri, Jan 28, 2011 at 12:50 PM, Gregory Crosswhite <gcross@phys.washington.edu> wrote:
Hey everyone,
To gather more data about what the community thinks an immutable byte sequence data structure should be called (given that "string" has already been taken), I have created the following poll:
https://catalyst.uw.edu/webq/survey/gcross/123312
If you have an opinion on the matter, please consider visiting the above link and submitting your favorite name.
Some names that have been tossed around are istring, immutable_string, chain, rope, yarn, twine, cord, but don't feel limited to these choices.
Cheers, Gregory Crosswhite
I suggested `bytes`. I think that this plays well with the STL style of keeping names short and succinct, and it also makes sense when considering that the compile-time constant ratio template is named `ratio`. To me, `chain`, `rope`, `yarn`, `twine`, and `cord` have special meanings or indicate something special about the implementation, especially `rope` and `cord` which make me think of the cord type that is provided with the Boehm garbage collector (http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/cordh.txt).
Hi, As you all describe strings as "sequences" of bytes or whatever, I proposed : sequence<char> and fixed_sequence<char> // but maybe fixed is not clear enough about the immutability? I often find that using the most describing word in the description of what we want to name is helpful. That said I'm might miss something that makes this proposition wrong as I'm not a native english speaker. Joël Lamotte.
participants (7)
-
Artyom -
Daniel Trebbien -
Dave Abrahams -
Gregory Crosswhite -
Klaim -
Matus Chochlik -
Robert Kawulak