For the record, i'm not actually opposed to allowing public fields to be introspected. However, as a practice, i don't believe in making any fields but static final ones public, so i'm not especially motivated here.
Perhaps we could start by allowing public static final methods? What do other dev folks think? On 8/25/06, Gyanesh M Khanolkar <[EMAIL PROTECTED]> wrote:
Hi, I have read in many forums for requests to read public fields ALSO incase the getters are missing. But it seems we are still going by the JavaBean specification which allows us to access the property ONLY via a getter variable. Preferably we would want to avoid the painful getters as it bloats up our already existing code. Would it be possible for you to reconsider this approach where $UserObj.FirstName will check with the getters : getFirstName() / getfirstName() and if both were not found, then it accesses the public variable FirstName. Introduction of this feature would be of great help as it helps us to reduce writing additional code which is often of no use. Regards Gyanesh
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
