Structs DO have constructors, but I found an answer with a quick
Google. In case anyone else is sad enough to care, structs have an
explicit but hidden default constructor whose purpose is to assign
default values to field members.
That's why you can't create an explicit default constructor on a
struct, the .Net framework creates one under the covers. This default
constructor is presumably used by the XmlSerializer.
Mystery solved.
bruce barker (sqlwork.com) wrote:
structs are not objects, but rather a value types. they are allocated on the
stack, rather than the heap. to improve value type performance, they do not
have contructors like objects.
-- bruce (sqlwork.com)
"Flinky Wisty Pomm" <Pa********@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com... Hi, this is just out of curiosity really. I had a struct, requirements
changed and I needed to inherit from it, so I made it into a class.
After the change, XmlSerializer choked because XmlSerializable classes
require a default constructor. Why don't structs?
