I have a data string that is defined as having two characters for the ID value, six characters for longitude, etc. "Fixed-length string" does not convey the requirement for internal bits of the string to be fixed-length as well.
|
|
The concept comes from punch cards and mechanical readers where field locations had to be set in hardware. It is called a:
A straightforward google search for fixed length record will find you lots of similar definitions. |
|||
|
|
|
I would call it "a data string made of fixed-length fields". A bit verbose, but precise enough, I think. |
|||
|
|
You could call it a data structure. Or, to be more precise, a data structure that happens to reside within a fixed length string. |
||||
|
Fixed-format string comes closest to the idea of a string whose costituents are all of fixed length. Borrowing fron the legacy concept of a fixed-format record where fields are always of the same length, this term however, avoids all references to the file-record system. So much so, I do not want to mention even 'data structure'. |
||||
|
|
|
This is squarely in my field, yet nothing that specific comes to mind. The length of the constituents of this data unit being fixed is not really its most important attribute. Once upon a time, if you used the word record that would instantly conjure up an image of some fixed length unit with fixed fields. One word which still carries those connotations might be block. Today, even if you are dealing with such a string, you're likely to make it "future proof" by writing the code so that it actually parses the pieces as if they were not fixed length (unless it is impossible to avoid relying on the fixed lengths due to some inherent ambiguity and lack of delimiting). Good question for programmers.stackexchange.com. |
|||
|
