Talk:Fixed length records

From Rosetta Code

reason for draft status

Btiffin (talk) 01:11, 14 October 2018 (UTC) Draft task due to it being a first attempt at posting tasks.

All tasks start out as draft tasks, no matter whether it be the first attempt at creating/posting tasks or not.
Drafts tasks are kept a draft task for several reasons,   some of which are:
  • at least 3 or 4 computer language entries should be entered so other people can see what is expected.
  • people can question and ask for clarification if any of the task's requirements need explaining.
  • sometimes the wording of the task may need polishing   (for clarity, succinctness, definitions, ...)
  • allow some time (days) for people to comment/observe the task's requirements and/or program solutions.
  -- Gerard Schildberger (talk) 00:53, 15 October 2018 (UTC)

Essentially a duplicate of Selective_File_Copy?

It seems to me that there isn't much substantial difference between this task and Selective_File_Copy, other than the length of the fixed size record. Seems like both want the user to read fixed sized records, manipulate the data in some simple way, than write out fixed sized records. Both tasks are pretty vague about what they are supposed to be demonstrating / accomplishing.

I also find it interesting that this has been pushed through to task status after less than 1 day while Selective_File_Copy is still a draft after more than 3 years and 16 implementations. --Thundergnat (talk) 11:50, 15 October 2018 (UTC)

Also, I am somewhat mystified how "Indented line 8" becomes "8 enil fo tuO" when reversed in the COBOL example. --Thundergnat (talk) 14:16, 15 October 2018 (UTC)