{"action":"created","issue":{"url":"https://api.github.com/repos/tkruse/cpplint/issues/19","repository_url":"https://api.github.com/repos/tkruse/cpplint","labels_url":"https://api.github.com/repos/tkruse/cpplint/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/tkruse/cpplint/issues/19/comments","events_url":"https://api.github.com/repos/tkruse/cpplint/issues/19/events","html_url":"https://github.com/tkruse/cpplint/issues/19","id":150564385,"number":19,"title":"Merge Cpplint Pull requests / fix issues","user":{"login":"tkruse","id":1525116,"avatar_url":"https://avatars.githubusercontent.com/u/1525116?v=3","gravatar_id":"","url":"https://api.github.com/users/tkruse","html_url":"https://github.com/tkruse","followers_url":"https://api.github.com/users/tkruse/followers","following_url":"https://api.github.com/users/tkruse/following{/other_user}","gists_url":"https://api.github.com/users/tkruse/gists{/gist_id}","starred_url":"https://api.github.com/users/tkruse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tkruse/subscriptions","organizations_url":"https://api.github.com/users/tkruse/orgs","repos_url":"https://api.github.com/users/tkruse/repos","events_url":"https://api.github.com/users/tkruse/events{/privacy}","received_events_url":"https://api.github.com/users/tkruse/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-04-23T15:21:50Z","updated_at":"2016-05-01T20:10:04Z","closed_at":null,"body":"@itamaro, @mattyclarkson, @massenz, @tychoish, @dirk-thomas, I took the liberty to make branches and pull requests from several outstanding PRs on https://github.com/google/styleguide. I believe that repo is practically dead, and anyway I don't see good reasons why a public linter should be kept in a single same repo as coding guidelines for various languages for Google employees.\r\n\r\nI mention you here because you all contributed patches to cpplint. I would like to merge the changes to make a new pypi release of cpplint. The PRs need to be rebased and reviewed, possibly also adding additional tests or consolidating. I'll eagerly merge PRs that have been reviewed by any of you (except by the authors themselves).\r\n\r\nIf you would like to comment or change your own PRs, or review any of the others, that would make things go faster.\r\n\r\n## Essential\r\n\r\n* [ ] #22 Fix issues with alternative file extensions\r\n* [ ] #6 Fix wrong report for \"public slots\" +  #8 Quick hack for QT\r\n* [ ] #9 Allow end-of-namespace lines that begin with whitespace.\r\n* [ ] #12 Python3000 (my master branch already has similar patches)\r\n* [ ] https://github.com/google/styleguide/issues/62 cpplint does not detect space before parens\r\n* [ ] make pychecker pass\r\n\r\n* [x] https://github.com/google/styleguide/issues/61 cpplint gives bogus error on rvalue reference\r\n* [x] #13 Explicit variadic constructors\r\n* [x] #14 Single line lambdas\r\n* [x] #16 Using namespace literals\r\n* [x] ~~#11 Added the extensions option to the CPPLINT.cfg option file~~\r\n* [x] #15 Ignore long Doxygen copydoc/copydetails/copybrief lines because doxygen cannot handle linewrap\r\n\r\n## Nice to have:\r\n* [ ] #7 The cpplint returns non-zero when there is at least one message.\r\n* [x] #10 Make output appear in the Visual Studio Error List\r\n* [ ] #18 Access keyword indent \r\n* [ ] #21 Added custom system headers section \r\n* [ ] https://github.com/google/styleguide/issues/14 Sonar-friendly output option\r\n* ~~#17 Add configuration option for file extensions~~\r\n"},"comment":{"url":"https://api.github.com/repos/tkruse/cpplint/issues/comments/216068915","html_url":"https://github.com/tkruse/cpplint/issues/19#issuecomment-216068915","issue_url":"https://api.github.com/repos/tkruse/cpplint/issues/19","id":216068915,"user":{"login":"massenz","id":1153951,"avatar_url":"https://avatars.githubusercontent.com/u/1153951?v=3","gravatar_id":"","url":"https://api.github.com/users/massenz","html_url":"https://github.com/massenz","followers_url":"https://api.github.com/users/massenz/followers","following_url":"https://api.github.com/users/massenz/following{/other_user}","gists_url":"https://api.github.com/users/massenz/gists{/gist_id}","starred_url":"https://api.github.com/users/massenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/massenz/subscriptions","organizations_url":"https://api.github.com/users/massenz/orgs","repos_url":"https://api.github.com/users/massenz/repos","events_url":"https://api.github.com/users/massenz/events{/privacy}","received_events_url":"https://api.github.com/users/massenz/received_events","type":"User","site_admin":false},"created_at":"2016-05-01T20:10:04Z","updated_at":"2016-05-01T20:10:04Z","body":"@tkruse - do you still need any work from me?\r\nFinally back, now have time to contribute to this, if desired.\r\n\r\nThere's also this fix (from my fork of `styleguide`):\r\nhttps://github.com/massenz/styleguide/commit/9c3afba6458d1b34b05fae88bdb30685dd5e7e1b\r\n\r\nTo me, the most pressing need would be to make this monster of non-PEP8-horribly-written single-file abomination into a more modular and more manageable set of modules.\r\n"}}