Prev: Net Framework Failed Install Issues
Next: "Add Webreference" in VS2008 .NET 2.0 project won't generate dynamiccode...
From: Peter Duniho on 14 Jan 2010 14:00 Jesse Houwing wrote: > Makes sense... Though they could have returned an array with the correct > size True. But� > without problems... Not necessarily. Second-guessing API design is fraught with error. You (and I) have no idea what led to the "always 13 elements" decision. It's entirely possible that requirement was inherited within .NET from some factor outside their control, such as an unmanaged API, and perhaps even a factor where it really does make more sense for the length of the array to always be fixed. I doubt that the existing design was chosen completely arbitrarily. In any case, it is what it is. :) Pete |