Yeah. 42. I know that answer \ud83d\ude42<\/p>\n\n\n\n
So far what we have is<\/p>\n\n\n\n
Module PictureMimicry\n\n Class MyPicture\n Function MyGraphics() as MyGraphics\n End Function\n End Class\n\n Class MyGraphics\n End Class\nEnd Module\n<\/code><\/pre>\n\n\n\nAnd now, for the answer, on how to make it so we can make the compiler catch the attempts to create a new MyGraphics.<\/p>\n\n\n\n
First we ABSOLUTELY put a protected constructor on MyGraphics. That will prevent EVERY attempt to create a new MyGraphics with the NEW operator. But now how does MyPicture create one to return it ?<\/p>\n\n\n\n
It doesnt \ud83d\ude42<\/p>\n\n\n\n
Remember we can set the SCOPE of items in a way that they can ONLY be used by code in the module. And since Xojo IS an OO language and support inheritance and polymorphism we can use that to our advantage.<\/p>\n\n\n\n
In such a language every subclass of a class IS also its parent class type. <\/p>\n\n\n\n
What we’re going to do is add a private subclass whose sole purpose is to allow us to create new instances. And we can return that subclass and the code outside the module will ONLY be able to use it as the parent class type because the subclass type is not know outside he module.<\/p>\n\n\n\n
The end result is this set up<\/p>\n\n\n\n
Module PictureMimicry\n\n Class MyPicture\n Function MyGraphics() as MyGraphics\n return new MyGraphicsSubclass\n End Function\n End Class\n\n Class MyGraphics\n Protected Sub Constructor()\n End Sub\n End Class\n\n Private Class MyGraphicsSubclass\n Inherits MyGraphics\n\n Public Sub Constructor()\n End Sub\n\n End Class\n\nEnd Module<\/code><\/pre>\n\n\n\nand now in the App Open event from the previous post<\/p>\n\n\n\n
dim p as MyPicture\ndim g as MyGraphics\n\np = new MyPicture\ng = new MyGraphics<\/code><\/pre>\n\n\n\nThe compiler will complain about the last line not being permitted. Exactly as we wanted.<\/p>\n\n\n\n
And this code<\/p>\n\n\n\n
Dim p As MyPicture\nDim g As MyGraphics\n\np = New MyPicture\ng = p.MyGraphics<\/code><\/pre>\n\n\n\nWorks exactly as we intended.<\/p>\n\n\n\n
You can now freely add methods to MyGraphics and MyPicture and know that none of your own code can accidentally create a MyGraphics in a way that you did not intend to permit.<\/p>\n\n\n\n
Code in a way the compiler can help you write code the way you intended it to work. Not just by convention or habit. But by design.<\/p>\n\n\n\n
Code for your own safety and sanity. Get the compiler to help you when it can.<\/p>\n","protected":false},"excerpt":{"rendered":"
Yeah. 42. I know that answer \ud83d\ude42 So far what we have is And now, for the answer, on how to make it so we can make the compiler catch the attempts to create a new MyGraphics. First we ABSOLUTELY put a protected constructor on MyGraphics. That will prevent EVERY attempt to create a new … <\/p>\n