Z
Zytan
Even for structs? But sometimes a struct is just something simple,
Actually, the readonly modifier could be useful. It doesn't allow
validation or letting the underlying implementation change, but in my
case, there is nothing to validate, it's just a storage place for
strings/ints, to *later* to analyzed, such as for network traffic. I
don't want to validate it on storage, I'll do that later. This struct
is storing to make it easier to analyze later, rather than attempting
to analyze too much info at once. And, the underlying structure will
never change (if it ever does, a lot more than this struct would have
to change).
I assume it is ok for me to use readonly. Some people must use it
properly somewhere, or it wouldn't be included in the language.
Zytan
Yes, that's true. I will do this.
Actually, the readonly modifier could be useful. It doesn't allow
validation or letting the underlying implementation change, but in my
case, there is nothing to validate, it's just a storage place for
strings/ints, to *later* to analyzed, such as for network traffic. I
don't want to validate it on storage, I'll do that later. This struct
is storing to make it easier to analyze later, rather than attempting
to analyze too much info at once. And, the underlying structure will
never change (if it ever does, a lot more than this struct would have
to change).
I assume it is ok for me to use readonly. Some people must use it
properly somewhere, or it wouldn't be included in the language.
Zytan