Talk:File input/output: Difference between revisions

m (Mortense moved page Talk:File IO to Talk:File input/output: Expansion.)
 
(3 intermediate revisions by 2 users not shown)
Line 24:
 
::On many systems and with many languages there are no special considerations for handling binary vs. text in files. Separate tasks for each could result in duplication without any clarification to the readership. Perhaps one task specifying processing of a binary file and a text file. One might have a task to read a specific binary file and a text file, extract some data from each, and then write the results to a text file. The code implementing that task could then highlight any differences in handling that are required by the language (as well as any portability features that show up for languages that are supported in multiple platforms). For example a Python example would show binfile.read() vs. txtfile.readline(). [[User:JimD|JimD]] 15:17, 20 November 2008 (UTC)
 
== Haskell issue ==
 
The current Haskell implementation does not comply with the requirement of intermediate variable. [[User:Marius|Marius Amado-Alves]] ([[User talk:Marius|talk]])
 
: Arguably, 'c' is an intermediate variable. (Also, please [[mw:Help:Signatures|sign]] your talk edits? I threw in a minimal basic signature for you, but the wiki does a much better job if you let it.)
 
::What 'c'? [[User:Marius|Marius Amado-Alves]] ([[User talk:Marius|talk]]) 18:23, 21 August 2019 (UTC)
 
:::Oops, I must have been looking at the following (hexscript) entry. Ignore my comment about c - that was a mistake. --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 18:37, 21 August 2019 (UTC)
 
: (But, that said, ... I can see a reasonable desire for alternate concepts of "reading the contents of a file into a variable" especially for the Haskell case. But there's a variety of those, and we didn't specify which, here. Still, there's certainly room for alternate implementations, on the page.) --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 15:53, 21 August 2019 (UTC)
6,951

edits