Re: SEEK_* enum values in SeekType



Michael,

On 19 Mar 2002, Michael Meeks wrote:

> 	Ok - so this problem is nasty; I think the best approach is to change
> these to SeekCur, SeekPos, SeekEnd etc. following the Java naming
> convention more.
> 
> 	The problems are:
> 
> 	a) We want to do this for everything really,
> 	b) We need to be able to measure the impact and get release team
> 	   approval first
> 	c) We need to do it fast.

I don't have good news for you -- if we change _every_ enum value for
StudlyCaps, the impact will be HUGE, it will take a lot of time, and if I
were the release team, frankly, I wouldn't approve it that late in the
game.

> 	Can you do an LXR search and find out which enumerations are used
> outside the core, what we would need to change to make it work, and how
> much it would break people.

I'll do the LXR query for SEEK_*, but if we change only SEEK_*, we'll have
an ugly inconsistency with other enumerations.

> 	Then we can think about doing it - really good that you've picked up on
> this now.

I wish I (or someone else) noticed it sooner -- like, half a year ago :(

-- 
   .--= ULLA! =---------------------.   `We are not here to give users what
   \     http://cactus.rulez.org     \   they want'  -- RMS, at GUADEC 2001
    `---= cactus cactus rulez org =---'
Semiconductor: part-time music director




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]