Fixing enum names in Phobos
Jonathan M Davis
jmdavisProg at gmx.com
Thu Aug 4 09:11:46 PDT 2011
On Thursday 04 August 2011 18:01:28 David Nadlinger wrote:
> On 8/4/11 5:59 PM, Jonathan M Davis wrote:
> > I think that it would be far better to just fix the names immediately.
>
> I'd argue not to touch std.socket though, this would unnecessarily break
> code that will be broken again (hopefully) soon once std.socket gets
> replaced.
Are there definitely plans to fix std.socket? I don't recall that one being
definitely planned for a redesign. If it is, then I completely agree with you,
but I don't really know much about std.socket (I've never used it). If it
needs a redesign, then it should get one (and hopefully sooner rather than
later), but I'm not aware of any plans to redesign it, and if such a redesign
is going to happen, _someone_ needs to do it, so we probably need to see if we
can find someone able and willing to do so. But if std.socket doesn't actually
need to be redesigned and isn't going to be redesigned, then it doesn't
necessarily make sense to skip renaming its enum values.
So, I agree as long as we're actually going to be redesigning std.socket, but
I'm not aware of any plans to redesign std.socket. We should probably have a
page somewhere which keeps track of planned major redesigns like that.
Sometimes, it's easy to forget what exactly is going on with it.
- Jonathan M Davis
More information about the Digitalmars-d
mailing list