Open arjenmarkus opened 4 years ago
I am pretty sure we discussed this at the last October Committee meeting and I thought this was generally approved, but I can't find the proposal right now. (Starting this February meeting, I plan to rigorously track every proposal and the associated discussion at GitHub issues here.)
I am pretty sure we discussed this at the last October Committee meeting and I thought this was generally approved, but I can't find the proposal right now. (Starting this February meeting, I plan to rigorously track every proposal and the associated discussion at GitHub issues here.)
See https://j3-fortran.org/doc/year/19/19-138r1.txt. The summary is
3 Specifications
A source line contains at most ten thousand characters.
A source statement contains at most one million characters.
Processors are required to be able to report too-long lines.
Continuation is unchanged, except that the limit of 255 is removed.
WG5 approved this for Fortran 202X at the Tokyo meeting August 2019..
Perfect :)
@arjenmarkus wrote:
Perfect :)
Can this issue be marked as "Completed" (or some such)?!
As this topic has already been discussed in the WG5 group, it can be closed.
Just done so.
Op vr 10 jan. 2020 om 14:59 schreef FortranFan notifications@github.com:
@arjenmarkus https://github.com/arjenmarkus wrote:
Perfect :)
Can this issue be marked as "Completed" (or some such)?!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/j3-fortran/fortran_proposals/issues/133?email_source=notifications&email_token=AAN6YR2UXHZTJFYWNJ3FOUTQ5B5N3A5CNFSM4KE2IJ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIT73SQ#issuecomment-573046218, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN6YR3ZUKB66VQY34DEB33Q5B5N3ANCNFSM4KE2IJ6Q .
I recommend keeping this issue open, despite there being an existing proposal and discussion at meeting. The rationale for it is that the issue doesn't get buried and people from the community can more easily discover it, support it, and give their two cents. By closing the issue, we're shutting down this side of the conversation.
Let's keep any issue open until it officially enters the language standard. If there is an existing proposal and discussion already, we can use a tag to mark this "in progress" or similar. @certik what do you think?
Yes, let's definitely keep the issue open until it becomes part of the standard. I added the appropriate labels for now.
It is a minor issue, but sometimes the restriction of at most 132 characters hinders the programmer - or some program generating source code from specifications (I am specifically thinking here of my "flemon"' parser generator). Would it not be nice to not have to worry too much about the line length? Note that I do not intend to write code with lines of more than 100 characters or whatever fits nicely on the screen (or the printout). It is just that in particular situations - generated code or deeply nested code - you run into the right-hand margin.