Differences between revisions 1 and 2
Revision 1 as of 2005-09-30 20:24:29
Size: 194
Editor: GaryBader
Comment:
Revision 2 as of 2005-09-30 20:35:54
Size: 694
Editor: mskresolve-b
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

EthanCerami -9/30/05 - Originally, I had the getters/setters use the same primitive types, e.g. boolean, double, String, etc. But, this becomes a problem for the getters. For example, if you request a boolean, but there is no value for this id/attributeName pair, what do you return? false? Hence, I switched to using wrappers. That way, if there is no id/attributeName pair, you get back a null. I then decided to keep the setters with primitive types, primarily for programmer convenience.

GaryBader -9/30/05 - why do the setters take basic types e.g. double and the getters return Object types e.g. Double? Would it be simpler for the user to expect one or the other consistently?

EthanCerami -9/30/05 - Originally, I had the getters/setters use the same primitive types, e.g. boolean, double, String, etc. But, this becomes a problem for the getters. For example, if you request a boolean, but there is no value for this id/attributeName pair, what do you return? false? Hence, I switched to using wrappers. That way, if there is no id/attributeName pair, you get back a null. I then decided to keep the setters with primitive types, primarily for programmer convenience.

RFC_1/RFC1_Comment_Getters_Setters (last edited 2009-02-12 01:03:29 by localhost)

Funding for Cytoscape is provided by a federal grant from the U.S. National Institute of General Medical Sciences (NIGMS) of the Na tional Institutes of Health (NIH) under award number GM070743-01. Corporate funding is provided through a contract from Unilever PLC.

MoinMoin Appliance - Powered by TurnKey Linux