2 Commits

Author	SHA1	Message	Date
yangguo@chromium.org	aa3518a0f3	Make sure files end with exactly one new line and police this in presubmit. ... The changes are (excluding presubmit.py) mechanical. I added the following lines after the check and iterated the presubmit script until all errors went away: f = open(name, "w"); if contents.endswith('\n\n'):   f.write(contents[0:-1]) else:   f.write(contents + '\n') R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/82803005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18017 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	2013-11-22 13:50:39 +00:00
mvstanton@chromium.org	d5e485a3cc	Change 'Parse error' to three more informative messages. ... Replace the 'unable_to_parse' key used in three places with three difference keys. Provide three more informative and less ambiguous error messages in place of 'Parse error'. Add three test/message cases to cover the new messages. BUG=2636 Review URL: https://codereview.chromium.org/14161007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@14462 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	2013-04-26 14:26:54 +00:00