{"action":"closed","issue":{"url":"https://api.github.com/repos/xdata-skylark/libskylark/issues/30","repository_url":"https://api.github.com/repos/xdata-skylark/libskylark","labels_url":"https://api.github.com/repos/xdata-skylark/libskylark/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/xdata-skylark/libskylark/issues/30/comments","events_url":"https://api.github.com/repos/xdata-skylark/libskylark/issues/30/events","html_url":"https://github.com/xdata-skylark/libskylark/issues/30","id":174635113,"number":30,"title":"Executing a Kernel: a nightmarish maze.","user":{"login":"jomsdev","id":3369356,"avatar_url":"https://avatars.githubusercontent.com/u/3369356?v=3","gravatar_id":"","url":"https://api.github.com/users/jomsdev","html_url":"https://github.com/jomsdev","followers_url":"https://api.github.com/users/jomsdev/followers","following_url":"https://api.github.com/users/jomsdev/following{/other_user}","gists_url":"https://api.github.com/users/jomsdev/gists{/gist_id}","starred_url":"https://api.github.com/users/jomsdev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jomsdev/subscriptions","organizations_url":"https://api.github.com/users/jomsdev/orgs","repos_url":"https://api.github.com/users/jomsdev/repos","events_url":"https://api.github.com/users/jomsdev/events{/privacy}","received_events_url":"https://api.github.com/users/jomsdev/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/xdata-skylark/libskylark/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-01T21:53:30Z","updated_at":"2016-10-12T23:04:21Z","closed_at":"2016-10-12T23:04:21Z","body":"Now all the flow is working but:\r\n\r\n- In the file [ckernel](https://github.com/xdata-skylark/libskylark/blob/capi/capi/ckernel.cpp#L11) the str2kernel_type function is using a macro defined in another file.\r\n\r\n- In the file [kernels.hpp](https://github.com/xdata-skylark/libskylark/blob/capi/ml/kernels.hpp#L78) the Gram() function defined inside a macro that will be expanded some lines below with multiple returns inside  the macro (which will finish the Gram() function) etc.. The flow of that functions is like a maze (macros expand before start to compile but the syntaxes make it easy confuse it with a function, etc). \r\n\r\nI am thinking about make it more elegant. Hints and Ideas will be welcome."}}
{"actor":{"display_login":"jomsdev"}}