Talk:Append a record to the end of a text file: Difference between revisions

→‎CSV?: Looks like something that's not what people call "CSV"
(→‎CSV?: Looks like something that's not what people call "CSV")
Line 11:
Is it supposed to be a CSV file? The description doesn't say anything about the file format, unless "passwd" implies some sort of format. Maybe the given records should be specified in the description. --[[User:Mwn3d|Mwn3d]] 23:57, 12 September 2011 (UTC)
 
:Agreed. Will do.
 
:The essence of the task is "Append a record to the end of a text file". Crudely speaking:
:* A record is something that has multi fields.
:* A text file is something that can be edited with "notepad"
:** in essence it does not contain "raw binary integers" etc.
:** The text file "record" represents the original record fields.
:I want to avoid simply appending random text to the end of an arbitrary file as nominally programs are (concurrently) manipulating (and storing) structures of data.
 
:[[User:NevilleDNZ|NevilleDNZ]] 01:44, 13 September 2011 (UTC)
::The given format does not look like CSV. While "colon-separated values" technically shortens to "CSV", [[wp:Comma-separated values|CSV]] looks like this:
value11,value12,value13 with spaces,value14
value21,value22,value23,value24 with spaces
::Commas are the only separator. The colons in the given format make it look like something else that we shouldn't call CSV. Is that what etc/passwd looks like? It would probably be best to say something like "the record's values are separated by commas, with values in composite items separated by commas (similar to Linux's /etc/passwd file)." If at all possible you might want to make the data structures involved in the record very very simple (i.e. no structs). That would make sure the focus is on what's in the task title. Stringifying a custom data structure is a different task (which we might not have yet...). --[[User:Mwn3d|Mwn3d]] 02:23, 13 September 2011 (UTC)
Anonymous user