Skip to content

question: is there a standard for 'shortest'?  #208

@newbie-02

Description

@newbie-02

not a 'pro' ... sorry,

there are probably different goals, styles and understandings about 'shortest'. E.g. performance and the preference of scientific notation to save the comparison against non-scientific, preference of 'standard' notation also with zeros at the end to be faster in a reconversion ( plain read, no 'E' calculations ), or lowercase 'e' instead of uppercase 'E' notation as STL represents it in
comment on issue #199 .

For compatibility between different implementations, and e.g. to be able to compare the results in tests letter by letter instead of after a - possibly error-prone - reconversion into a binary figure, it would be nice to have a standard that everyone follows, or at least that they offer as an option.

After other experiences in IT I have to assume that there already are about a dozen standards and they argue about 'e' vs. 'E' or 'implementors choice' or 0.01 vs. 1E-2 or 'implementors choice' and the like, but I couldn't find one.

Is such already around, or is anyone in a position to initiate a standardization?
My suggestions would be:

  1. standard vs. scientific notation acc. shortest, saves space,
  2. ties to non-scientific, human friendly, easier str-to-bin,
  3. 'E' and not 'e', as it is common use IMHO,

thanks for any help and hints

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions