Bug? Private Process_Globals show when compiling code module to library

[jmon]

Hi,

This one is not a big deal, but I noticed that when I export a code module to a library, the "Private Sub Process_Globals" still shows in the list of methods of the library. The weird thing is that it is hidden when the code module is not compiled to library.

'Static code module
Private Sub Process_Globals
    Private JOColor As JavaObject
End Sub

- >

As I said, it's not a big deal, it's just aesthetic. Still I have a question: What is the purpose of being able to access the process_globals from the method list? Why isn't it private by default?

Thanks and have a nice week end!

 

[Erel]

It is public in the library because of technical reasons (the method must be exposed in the XML file).

The sub is not private by default as I find it confusing that the place to declare public variables is inside a private sub.

 

[jmon]

Ok, I see, it makes sense. Thanks for your explanations.