{"comment":{"url":"https://api.github.com/repos/jruby/jruby/comments/13235403","html_url":"https://github.com/jruby/jruby/commit/053458a3106d535809748aacfe25c7863288e7c6#commitcomment-13235403","id":13235403,"user":{"login":"jtulach","id":1842422,"avatar_url":"https://avatars.githubusercontent.com/u/1842422?v=3","gravatar_id":"","url":"https://api.github.com/users/jtulach","html_url":"https://github.com/jtulach","followers_url":"https://api.github.com/users/jtulach/followers","following_url":"https://api.github.com/users/jtulach/following{/other_user}","gists_url":"https://api.github.com/users/jtulach/gists{/gist_id}","starred_url":"https://api.github.com/users/jtulach/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jtulach/subscriptions","organizations_url":"https://api.github.com/users/jtulach/orgs","repos_url":"https://api.github.com/users/jtulach/repos","events_url":"https://api.github.com/users/jtulach/events{/privacy}","received_events_url":"https://api.github.com/users/jtulach/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":"","commit_id":"053458a3106d535809748aacfe25c7863288e7c6","created_at":"2015-09-15T12:08:55Z","updated_at":"2015-09-15T12:08:55Z","body":"I tried to add some examples with languages I knew (e.g. Java, C, possibly JavaScript) into the Truffle documentation. Do you want to have your own document (pros: you control it, cons: nobody finds it) or would you consider to add the sample Ruby code into the Javadoc of Truffle?\r\n\r\nNetBeans has a concept of non-normative sections in Javadoc (like [createAndOpen](http://bits.netbeans.org/8.0/javadoc/org-openide-filesystems/org/openide/filesystems/FileObject.html#createAndOpen%28java.lang.String%29) and [addRecursiveListener](http://bits.netbeans.org/8.0/javadoc/org-openide-filesystems/org/openide/filesystems/FileObject.html#addRecursiveListener%28org.openide.filesystems.FileChangeListener%29)). It tries to explain how some API concept are really implemented in parts of the system that don't have their own API/documentation, but are essential for understanding how the API behaves.\r\n\r\nMaybe it would be beneficial to include the Ruby samples next to the Message elements (pros: instantly ready for API readers, cons: hard to keep them in sync)!?"}}