Cauê
Well I was very surprised that my changed version worked without
namespaces, try it. I don't believe Sandy uses namespaces. So for a
lite engine I am not quite so convinced they are needed. Using
untyped means you can keep access private from end users but use them
internally, surely 74 uses must have some impact on performance
especially in a few cases of where they are used? Maybe if you have a
some harsh tests you could see if it makes a difference by comparing
the zip I posted with the current version, maybe the difference is not
significant.
Cheers
;j
On 7 Nov 2010, at 20:41, Cauê Waneck wrote:
Hey Justin!
If the haxe community are concentrating on just away rather than
sandy, I would like to see hsl or similar and bsp collision make it
into the haxe build, I am sure that could be implemented on the
current version while Caue works on molehill, well I need bsp
collision anyway.
The plan is to release the haXe port of the main engine on the next
major release. Can you wait on this? Porting BSP to lite wouldn't be
so trivial, so that would mean porting the main engine's state now
to haXe.
Flash namespaces are slower than the way haXe does it
Really ok, would it be worth me checking since I have both builds...
what might check the differences, do you have an idea on a good
test, I am not sure the way the injection works is as heavy as
normal flash namespaces but I might be wrong, also would be good to
see what difference using untyped and no namespace. Is there an
extreme example I should throw at it?
I don't think that the speed will be noticeable, as the real
performance hog are the draw calls... But anyway I can't see any
good side in using flash namespaces! Are there?
Cheers
;j
