Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

SO vote to reopen: protected visibility 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I'm not much of a Stackoverflow user. However it doesn't strike me as a place designed to handle opinion-based questions. chaos' suggested rewrite:

    what reasons are there to use protected members and/or to avoid them?

    seems a little better, but I think the question still needs to be more detailed. Perhaps something along the lines of:

    I have a class (X) and its child class (X::Y). X has a variable Z for some purpose. It doesn't make sense (for some reason) to make Z an attribute of X::Y but X::Y still needs to be able to access Z. I could implement it as a protected member, or I could expose it some other way. What is the correct approach in this situation and why?

    I think the problem with your original question is that it is scope-less. Protected variables have some advantages and some disadvantages. However it's difficult to answer with something that would be relevant to the question because it's too hard to guess what you were thinking when you wrote it.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.