{"action":"created","issue":{"url":"https://api.github.com/repos/atilaneves/reggae/issues/2","labels_url":"https://api.github.com/repos/atilaneves/reggae/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/atilaneves/reggae/issues/2/comments","events_url":"https://api.github.com/repos/atilaneves/reggae/issues/2/events","html_url":"https://github.com/atilaneves/reggae/issues/2","id":84846678,"number":2,"title":"Improve clarity of \"magic\" rules","user":{"login":"Dicebot","id":1132234,"avatar_url":"https://avatars.githubusercontent.com/u/1132234?v=3","gravatar_id":"","url":"https://api.github.com/users/Dicebot","html_url":"https://github.com/Dicebot","followers_url":"https://api.github.com/users/Dicebot/followers","following_url":"https://api.github.com/users/Dicebot/following{/other_user}","gists_url":"https://api.github.com/users/Dicebot/gists{/gist_id}","starred_url":"https://api.github.com/users/Dicebot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Dicebot/subscriptions","organizations_url":"https://api.github.com/users/Dicebot/orgs","repos_url":"https://api.github.com/users/Dicebot/repos","events_url":"https://api.github.com/users/Dicebot/events{/privacy}","received_events_url":"https://api.github.com/users/Dicebot/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/atilaneves/reggae/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-04T01:09:58Z","updated_at":"2015-06-12T15:37:12Z","closed_at":null,"body":"Currently higher level rules like `dubMainTarget` or `dCompile` are overly magical in both naming and implementation. It would improve learning curve a lot if `reggae` defined standard naming rules for higher level targets and separated their implementations in dedicated package/modules. Former would help to guess needed names without referring to documentaiton all the time, latter would provide nice examples of how one can define own higher level rules.\r\n\r\nIt is also worth noting that it isn't really important to go for shorter names for such symbols. Build systems are usually written once but read / maintained very often, as such, reading clarity and unambiguity takes absolute priority."},"comment":{"url":"https://api.github.com/repos/atilaneves/reggae/issues/comments/111530443","html_url":"https://github.com/atilaneves/reggae/issues/2#issuecomment-111530443","issue_url":"https://api.github.com/repos/atilaneves/reggae/issues/2","id":111530443,"user":{"login":"atilaneves","id":4956425,"avatar_url":"https://avatars.githubusercontent.com/u/4956425?v=3","gravatar_id":"","url":"https://api.github.com/users/atilaneves","html_url":"https://github.com/atilaneves","followers_url":"https://api.github.com/users/atilaneves/followers","following_url":"https://api.github.com/users/atilaneves/following{/other_user}","gists_url":"https://api.github.com/users/atilaneves/gists{/gist_id}","starred_url":"https://api.github.com/users/atilaneves/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/atilaneves/subscriptions","organizations_url":"https://api.github.com/users/atilaneves/orgs","repos_url":"https://api.github.com/users/atilaneves/repos","events_url":"https://api.github.com/users/atilaneves/events{/privacy}","received_events_url":"https://api.github.com/users/atilaneves/received_events","type":"User","site_admin":false},"created_at":"2015-06-12T15:37:12Z","updated_at":"2015-06-12T15:37:12Z","body":"I _think_ I've fixed this. I consolidated all the C, C++ and D rules with no difference in naming, and centralised all \"special\" commands in `build.Command.builtinTemplate`. I guess I should write docs for this, I'm not sure if what's here already is enough. Please let me know."}}