Hi,

Sorry autocorrect seems to have got the better of me - correcting:

I think you are forgetting the optimisation that goes on, yes the source code 
has a few more lines of code, but hardly double the size.

Perhaps we can come up with some rules/guildlines to what PAYG actually is? Say 
no more than 5% or 10% final size or runtime cost?

In this case the code has zero cost re final size or practical runtime 
performance (and extra null check on the JS side) and zero cost on the AS side.

Thanks,
Justin

Reply via email to