[
https://issues.apache.org/jira/browse/COUCHDB-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142507#comment-13142507
]
Noah Slater commented on COUCHDB-1329:
--------------------------------------
It's better than that.
POSIX defines a text file as:
"A file that contains characters organized into zero or more lines[...]"
And a line as:
"A sequence of zero or more non- <newline> characters plus a terminating
<newline> character."
And to really drive it home, it defines an incomplete line as:
"A sequence of one or more non- <newline> characters at the end of the file."
Strictly speaking, if the file does not end in a newline, it's a binary file,
as far as POSIX is concerned.
Just sayin', yo.
cf. http://pubs.opengroup.org/onlinepubs/9699919799/
> couch_js/utf8.h:19:7: error: no newline at end of file
> ------------------------------------------------------
>
> Key: COUCHDB-1329
> URL: https://issues.apache.org/jira/browse/COUCHDB-1329
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
> Affects Versions: 1.1.1
> Environment: likely anybody compiling with gcc -pedantic or -Werror
> Reporter: Dave Cottlehuber
> Priority: Trivial
> Fix For: 1.1.2
>
>
> ISO C 1999 requires a newline at the end of every non-blank source file:
> http://c0x.coding-guidelines.com/5.1.1.2.html vis
> "123 A source file that is not empty shall end in a new-line
> character, which shall not be immediately preceded by a backslash
> character before any such splicing takes place. "
> Thanks Mike Kimber for reporting this bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
