on ‎2024 Jun 27 11:19 AM
Hi !
Maybe it's a dumb question... But I'm always wondered how others developers named their global classes, because our namespace (Z & Y) is pretty limited since everything created in the repository can be created once (for the same type). I would loved a solution where the namespace is linked to a package and so it will be possible to name 2 repository objects identically into 2 separate package, sweet dream.
Because of this, I often find my self using local classes in my programs, I find them more flexible and I can avoid to pollute unnecessarily the repository with odd names. But there are costs, one of them is reusability. Of course, I create global classe when it's make sense, like business object that I know there will be only one classe like ZCL_EQUIPEMENT or ZCL_DELIVERY (with some exceptions to the rule of course) or classes with clear boundaries.
But what about classes like MODEL / DAO / VIEW / CONTROLLER and so on ? If we are using MVC pattern in our development, we have to deal with this classes in multiples reports, so if global, name conflict may happen when for example 2 MODEL in different applications are created with slightly different interface but with the same semantic.
What are your recommandation about it ?
Thanks !
Request clarification before answering.
| User | Count |
|---|---|
| 7 | |
| 7 | |
| 7 | |
| 7 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.