RS>   But in this case you didn't place public data at the top.
RS>   You did exactly what is above, which is place private
RS>   members at the top.  My question is, if the data is private
RS>   and it is at the top, before any access specifiers, why
RS>   would you place a private tag before it, when the access
RS>   is already private by default?
   If you can see no reason, then it stands to odds that there
   may not be one. In this case, you are absolutely correct.
   There is no reason. It just is that way. :)
   I didn't mean to confuse you by it. Not that we don't
   sometimes overlook a reason for things that defy logic,
   but in the present case, it is just from force of habit.
   I just usually put private members last, and therefore
   have the habit of defining them as private, even though
   it would have, in this case, been the default.
> ] Love is not blind, but sometimes it looks the other way.....
---
---------------