Re^2: Advice please on variable naming style in modules

Could be I was misleading you by a typo: App::Widget returns $widget, App::Widget::Menu returns $menu.

The thing is, both App::Widget and App::Widget::Menu at times want to be able to access settings stored in App's $self. You can use a jump-the-hoops-method like my $self_of_the_topmost_level = wxTheApp->GetTopWindow(); (in a Wx app) to get that.

Question is: what's a sane name for $self_of_the_topmost_level when it resides next to a "local" $self?

Comment on Re^2: Advice please on variable naming style in modules Download Code

Replies are listed 'Best First'.
Re^3: Advice please on variable naming style in modules by Jenda (Abbot) on Aug 22, 2012 at 14:51 UTC
What's "self" to you is isync to me. If the menu needs access to the top window, it should have a $top_window. The fact that within the methods of the top window the same reference will be in a variable called $self is irrelevant. To the method within the menu it's $top_window, not $self. <!-- Node text goes above. Div tags should contain sig only -- > Jenda Enoch was right! Enjoy the last years of Rome.	[reply]
Re^4: Advice please on variable naming style in modules by isync (Hermit) on Aug 22, 2012 at 21:08 UTC
Right, and more or less what tye and I agreed upon: what seems to make sense is: it's $self in the module and a var-name that reflects function everywhere else - as an example, for the $self of App, this could be $app (reflecting function), or could be $top_window (if you favour denoting hierarchical meaning).	[reply]