Anonymous user
Talk:Price fraction: Difference between revisions
→Representing the data
(→Representing the data: Standarization.) |
|||
Line 73:
In an "strongly specified" sort of problem, the specification would be set in stone and the developers' insights would not be relevant to the specification.
: I'd be open to standardizing on CSV as a format for tabular data, and hold a strong recommendation that tasks that make use of tabular data present it in CSV, and that examples that make use of it import it from such. It depends on it being fairly portable; one would be increasing the complexity of every task to including either processing stream input or file input. --[[User:Short Circuit|Michael Mol]] 21:36, 18 March 2010 (UTC)
:: Real code parses it in whatever idiotic form the local legislature decides to publish it in. These days, that means whatever format one gets when one cuts-n-pastes it out of some PDF… –[[User:Dkf|Donal Fellows]] 22:27, 18 March 2010 (UTC)
| |||