Simple approach to call private methods in modules

[NoahPhense]

Hi NoahPhense,

Please take a look at this post by TI-994A:

http://www.purebasic.fr/english/viewtop ... 43#p418143

I didn't know anything about Modules. I found this very helpful.
I hope you do, too.

Thanks David, helps a lot.

- np

[USCode]

Just be open minded.
But not too open minded, otherwise your brain could fall out.

That's what I'm afraid of!
I'll take a look at it when the final version is released.
Initially it sounded like namespaces to me but I think other folks have pointed out that is not correct.

[c4s]

[...] Over time, classes become dependent on the inner workings of other classes. [...]

If a programmer knows how to code properly, sticks to general coding standards and complies with the documented behavior (most important!), this would never happen.

Never say never.
Otherwise people reading this will think you are too far removed from reality.

It's funny because I knew that the "never" would cause some discussion.

Still, let's say you're working in a team. Now the only thing you know about a class is its signature and the documentation, because you didn't implement it yourself (and you don't have access to the source). If you want to interact with that class you can only rely on the documented behavior. So I really don't see how one could get dependent on the inner workings...

[fsw]

Just saying: experience taught me otherwise.
If your experience differs - be happy!

[Fred]

Just be open minded.
But not too open minded, otherwise your brain could fall out.

That's what I'm afraid of!
I'll take a look at it when the final version is released.
Initially it sounded like namespaces to me but I think other folks have pointed out that is not correct.

It's like namespace.

[USCode]

Just be open minded.
But not too open minded, otherwise your brain could fall out.

That's what I'm afraid of!
I'll take a look at it when the final version is released.
Initially it sounded like namespaces to me but I think other folks have pointed out that is not correct.

It's like namespace.

Excellent, good work Fred!

[BorisTheOld]

Still, let's say you're working in a team. Now the only thing you know about a class is its signature and the documentation, because you didn't implement it yourself (and you don't have access to the source). If you want to interact with that class you can only rely on the documented behavior. So I really don't see how one could get dependent on the inner workings...

The problem is not with the use of a class, but with the maintenance of class code in complex systems with hundreds, or thousands, of interrelated classes and multiple levels of inheritance.

Over the years, classes evolve to meet the demands of new applications. As a result, inherited methods often need to handle conflicting situations. This is where the problems begin. Eventually, as more and more classes evolve in this way, the whole system begins to collapse -- maintenance and bug fixing becomes a major problem.

In theory this should never happen, but the universe tends to be a fickle place in which to strive for perfection.