Here again the request, it is really very important.
I accidentally found the error in my app.
I defined this variable in main module and in a library, so compilation was not possible.
All error messages had no indication of the variable.
Although having the possibility to define private a type can be useful, I did not understand your post (you've probably used the term variable instead of type).
I can have a type defined in a class of a library, like:
Type tPoint(x as int, y as int)
and the same in a project without "conflicts".
[beautiful, unuseful, almost empty library named Buttami2.jar with that type defined]
Although having the possibility to define private a type can be useful, I did not understand your post (you've probably used the term variable instead of type).
I'm sure that private types will be added at some point. Still, it is not recommended to create a type named Point. Add a two or three letter prefix (ex: FPPoint).
I'm sure that private types will be added at some point. Still, it is not recommended to create a type named Point. Add a two or three letter prefix (ex: FPPoint).
I'm sure that private types will be added at some point. Still, it is not recommended to create a type named Point. Add a two or three letter prefix (ex: FPPoint).