Re: Direct3D Tutorial 8 / has VS is
Posted: March 9th, 2019, 7:07 am
Hi all, apologies for not checking in for a few days. Thanks for inputting. Normally when I start posting on threads they die... On any forum. lol
Papa - it was a question of that specific example but also obviously in applying it general in a similar situation. The extension you talk about is what I was finally understanding with your mouse server example. I guess yeh, like you I am currently in that phase where I'm putting pure encapsulation over anything else and need to unlearn the lessons from university that made it the be-all-end-all.
I fully agree with your rant on children being extensions of the parents. You could access the "private" parent members if they were protected though right? But then if the child becomes a parent, those are now private in the child and the grandchild couldn't see them so only valid for one level of inheritance. Or I might have misunderstood / applied assumptive understanding to this.
Thanks for the links chili, I'm checking them out. I wish I'd gotten into software development straight out of university, and somewhere that makes software properly (FORMAL requirements gathering, design, testing, documentation, etc.) instead of using the "agile" methodology (in my experience this has meant hacking code out and testing / getting customers to test until it works). So yeah I'd love to do thing properly and know proper software engineering but I spend my life with the opportunities I've had available.
I think I need more time experiencing these new-to-me things to get comfortable with them. Eventually something clicks and I get it or at least come to terms with being OK with doing it that way lol.
I've actually been looking at some other youtubes on rule of 3, && (copy asign and copy constructor) and other basic C++ stuff again (by other people, sorry chili :\ lol ). It is good to refresh as I almost completely forget all the whys and hows but when I see the vids I'm understanding and remembering along with it, which is a good sign.
I also think some language features are odd. One in particular that I keep forgetting that is also a thing in C# is private members can be accessed by another instance of the same class. That just kinda blows my mind as it just seems to destroy the point of all this encapsulation that is a major benefit of oop. I don't see a case where this is really that beneficial, and especially not in a way that it is used more commonly than not that would warrant it being a thing. I guess this is one of those things that shows that encapsulation isn't truly what oop is ALL about.
It's amazing that you're (Papa) actually understanding more about what I'm really saying (my hang-ups with language quirks and oop not being as I thought it would be) through what I've actually said, but you're right!
Papa - it was a question of that specific example but also obviously in applying it general in a similar situation. The extension you talk about is what I was finally understanding with your mouse server example. I guess yeh, like you I am currently in that phase where I'm putting pure encapsulation over anything else and need to unlearn the lessons from university that made it the be-all-end-all.
I fully agree with your rant on children being extensions of the parents. You could access the "private" parent members if they were protected though right? But then if the child becomes a parent, those are now private in the child and the grandchild couldn't see them so only valid for one level of inheritance. Or I might have misunderstood / applied assumptive understanding to this.
Thanks for the links chili, I'm checking them out. I wish I'd gotten into software development straight out of university, and somewhere that makes software properly (FORMAL requirements gathering, design, testing, documentation, etc.) instead of using the "agile" methodology (in my experience this has meant hacking code out and testing / getting customers to test until it works). So yeah I'd love to do thing properly and know proper software engineering but I spend my life with the opportunities I've had available.
I think I need more time experiencing these new-to-me things to get comfortable with them. Eventually something clicks and I get it or at least come to terms with being OK with doing it that way lol.
I've actually been looking at some other youtubes on rule of 3, && (copy asign and copy constructor) and other basic C++ stuff again (by other people, sorry chili :\ lol ). It is good to refresh as I almost completely forget all the whys and hows but when I see the vids I'm understanding and remembering along with it, which is a good sign.
I also think some language features are odd. One in particular that I keep forgetting that is also a thing in C# is private members can be accessed by another instance of the same class. That just kinda blows my mind as it just seems to destroy the point of all this encapsulation that is a major benefit of oop. I don't see a case where this is really that beneficial, and especially not in a way that it is used more commonly than not that would warrant it being a thing. I guess this is one of those things that shows that encapsulation isn't truly what oop is ALL about.
It's amazing that you're (Papa) actually understanding more about what I'm really saying (my hang-ups with language quirks and oop not being as I thought it would be) through what I've actually said, but you're right!