Closed delahee closed 11 years ago
Hi
The macro is here : https://github.com/shoebox/inthebox-macros and already haxe 3 compatible
The first version was very "raw", the haxe3 version is much more cleaner and optimized ( was easier with the new haxe 3 macros features )
Great thanks ! :)
2013/7/25 Johann Martinache notifications@github.com
Hi
The macro is here : https://github.com/shoebox/inthebox-macros and already haxe 3 compatible
The first version was very "raw", the haxe3 version is much more cleaner and optimized ( was easier with the new haxe 3 macros features )
— Reply to this email directly or view it on GitHubhttps://github.com/shoebox/HyperTouch/issues/8#issuecomment-21542069 .
David Elahee
Please forgive me for what follows, but...if you don't mind a little observation... 3 segment namespacing is atrocious when i retrieve these code, first thing first i remove all these and replace by just 1 or 2 at worst:)...( lest than 1 syllabe is all the more finer ).
At MT we barely use namespace because in the end they are cognitive pollutions. I dont mean offense at all and hope for shorter future !
Sorry, I needed to say it :)
Thanks for your great work !
2013/7/25 David Elahee david.elahee@gmail.com
Great thanks ! :)
2013/7/25 Johann Martinache notifications@github.com
Hi
The macro is here : https://github.com/shoebox/inthebox-macros and already haxe 3 compatible
The first version was very "raw", the haxe3 version is much more cleaner and optimized ( was easier with the new haxe 3 macros features )
— Reply to this email directly or view it on GitHubhttps://github.com/shoebox/HyperTouch/issues/8#issuecomment-21542069 .
David Elahee
David Elahee
You have a "ShortCuts" class at the package root, made for lazy people ( like me ! ) :)
Anyway i like to keep namespaces, for avoiding file name collisions, especially when your are using by example a bunch of native extensions...
By the way, you could easily create an alias for any class in haxe :) if you want to keep then shorts.
didn't found another tracker so i post here :
1- Whence return type is not specified, the lib should throw a compile error, we preferre to ignore by adding:
static private function _get_package_return_type( t : ComplexType ) : String{ if ( t == null ) return 'Void';
but it must be better to send error
2- whence porting to haxe3 it shows there are many unmatched switch, they should send back null and we have the feeling it should sometime get processed :)
Good work anyway !