Comment #2 on issue 520 by adamn...@gmail.com: System.DataTypes is writeable http://code.google.com/p/gambas/issues/detail?id=520
I have been thinking about this and I am not sure whether creating a new array is the best answer. My problem arose when a reference was set to the property: myTypes = System.DataTypes which was subsequently modified with all the locally declared (public) types in the application. This was fine until the same routine was called again. So I got 2 copies of each local datatype in the array. That problem I have solved by using myTypes=System.DataTypes.Copy() AddLocalTypes(myTypes) So, AFAIC, this issue can be closed. Always creating a new array may cause problems where the programmer is explicitly trying to get a pointer to System.Datatypes and a subsequent reference will return a different address. (That's what I have been thinking anyway.) cheers Bruce -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
