Timeline for Compatibility of Enum Vs. string constants
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2018 at 15:54 | history | edited | svick | CC BY-SA 3.0 |
word
|
| Jan 26, 2018 at 15:42 | vote | accept | Yosi Dahari | ||
| Nov 6, 2013 at 19:48 | comment | added | Jon Raynor | Usually enums are serailized as names, not integers, although you can override this behavior. Example [XmlEnum("0")] Error= 0 if you wanted to emit the integer. | |
| Nov 6, 2013 at 15:56 | comment | added | svick | @Yosi That depends on the deserializer. In any case, you usually can't expect old code to handle new format correctly. | |
| Nov 6, 2013 at 15:41 | comment | added | Yosi Dahari |
Won't trying to deserialize Timeout = 3 (from the new version of TaskEndState) with an old version TaskEndState fail?
|
|
| Nov 6, 2013 at 15:37 | comment | added | svick | @Yosi You say string is better than enum, because of versioning issues. I'm saying you can solve those while still using enum. How does that not answer the question? | |
| Nov 6, 2013 at 15:35 | comment | added | Yosi Dahari | Nice point, but the question is about comparison vs. const string. | |
| Nov 6, 2013 at 15:33 | history | answered | svick | CC BY-SA 3.0 |