Why not add a scale for accessing both scaleX and scaleY (class extensions in as3?)

Question

I've considered and am suggesting there be a scale for both scaleX and scaleY (via a setter & getter function)
I think that one might get confused trying to get a value out of scale if scaleX and scaleY are different, but...
You could throw an error when using a variable scale (getter only) if they (scaleX&scaleY) are different, and return the value if they are the same.
It could throw more a warning and return the scaleX or scaleY or an average, and or possible have a policy (although again I can see this may seem potentially more confusing.)
I remember with ObjectiveC you could/can create a class extension that would extend a class that already exists pervasively like String.
This way you could alter functionality like this where all onjects have inheritend from a DisplayObject or whereever scaleX & scaleY are. Subclass as an Extension Class this deep lying class and add that kind of ability without needing to do it to all of your higher level classes (or other such tricks String Utility Classes etc.), which as I recall existed in ObjectiveC (and other langauges) no doubt because it was simply impossible to achieve the same effect any other way.
Is there such a way in AS3 to extend a class? Is it impossible for some reason?
May appologies if I've got the terminalogy wrong, please clarify if I'm searching for the wrong keyword on this thanks.
Anyway I still think putting something like
myCircle.scaleX *= 0.9;
myCircle.scaleY *= 0.9;
or
myCircle.scaleY = myCircle.scaleX *= 0.9;
or
myCircle.scaleX *= 0.9;
myCircle.scaleY = myCircle.scaleX;
is not as nice clean as
myCircle.scale *= 0.9;
would be. I think my thoughts on explaination for why and a simple possible selection of solutions (throw catchable/discargable errors/warning or alterable policies).

Answer 1

TCP has retry logic. The timeout period varies by OS and configuration. TCP will typically retry three times and wait for the timeout period to expire before reporting an error. I do not believe any OS will fail in less than two minutes with the standard timeout and some systems go to 5 minutes.