Cymbiola irvinae
Cymbiola irvinae is a species of sea snail, a marine gastropod mollusc in the family Volutidae, the volutes.[1]
| Cymbiola irvinae | |
|---|---|
| Scientific classification | |
| Kingdom: | |
| Phylum: | |
| Class: | |
| (unranked): | |
| Superfamily: | |
| Family: | |
| Subfamily: | |
| Genus: | |
| Subgenus: | |
| Species: | C. irvinae |
| Binomial name | |
| Cymbiola irvinae (Smith, 1909) | |
Description
Distribution
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.
gollark: Probably. The main issue I can see is that you would have to rewrite the entire metadata block on changes, because start/end in XTMF are offsets from the metadata region's end.
gollark: I thought about that, but:- strings in a binary format will be about the same length- integers will have some space saving, but I don't think it's very significant- it would, in a custom one, be harder to represent complex objects and stuff, which some extensions may be use- you could get some savings by removing strings like "title" which XTMF repeats a lot, but at the cost of it no longer being self-describing, making extensions harder and making debugging more annoying- I am not convinced that metadata size is a significant issue
gollark: I mean, "XTMF with CBOR/msgpack and compression" was being considered as a hypothetical "XTMF2", but I'd definitely want something, well, self-describing.
References
- Cymbiola irvinae (Smith, 1909). Retrieved through: World Register of Marine Species.
External links
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.