HasOwnProperty only for public?

Question

Trying to optionally call a method only if it exists:
private function _upload():void {
// first see if we have any custom handling that needs to be
done...
if(this.hasOwnProperty('upload') && this['upload']()
== false) {
// custom handling told us to stop processing!
return;
For some reason upload() only gets called if it is public. Is
this how it is supposed to work, or are the names mangled or
something? Is there some other way to test for a method that works
for protected/private methods/variables?
Thanks.

Answer 1

"slaingod" <[email protected]> wrote in
message
news:[email protected]...
> Thanks, ntsii,
> Yea I've just bit the bullet and made everything public.
Basically this is
> a
> poor man's subclassing using includes.
>
> Amy,
> Sorry if you somehow took offense at what I typed, but
my post count is
> over
> 300 and most of those are me answering questions on this
forum, so I'm
> pretty
> sure how it works.
Remember, everyone who posts here doesn't just automagically
know who you
are and what your level of expertise is, so it's completely
reasonable to
try to eliminate the possibility you're not trying to access
private methods
from outside the class and to ensure there actually _is_ an
upload property
to look at. Not everyone on here is at a level where it's
possible to
automatically assume that their assumptions about what they
are seeing are
right. In fact, 90+% of the time on here when posters think
they know why
something is happening, they are wrong.
> I thought my original question was pretty
straightforward to anyone who
> might
> know the answer.
>
> To explain my use case:
>
> I make a number of sites that have a large amount of
overlap in the 'user
> uploads' area, examples like:
>
>
http://www.pinktogether.com
>
http://www.klondikecontest.com/videos.aspx
>
http://www.benjerry.com/imagine/
>
http://posewood2.ugenmedia.com
>
> As such, a core piece of functionality stays (mostly)
the same for each
> site,
> so I have moved that core functionality into shared
include files. So if
> a
> component needs registration functionality, I just
include Register.as.
> If it
> also needs upload functionality, I also include
Upload.as.
>
> Internally in these shared includes, the code makes
calls like:
> //public function upload():Boolean
> public function _upload():void {
> // first see if we have any custom handling that needs
to be done...
> if(this.hasOwnProperty('upload') &&
this['upload']() == false) {
> // custom handling told us to stop processing!
> return;
> }
>
> ....(default code here)....
> }
>
> This cuts down on the cut and paste tremendously that
would be required by
> using subclasses, etc. There may be some esoteric way of
doing this
> 'right'
> using interfaces, classes, etc., but this is a very
cheap way of achieving
> 90%
> of the code reuse I want, at a very low technical
barrier for others who
> might
> need to use my code as well.
You may want to look at the decorator pattern.
HTH;
Amy