So, given the below, looks like we've got everything sewn up and the long-awaited day of the STM merge is upon us.
Charles, care to do the honors? On Tue, Aug 15, 2006 at 06:31:38PM -0400, Charles Reiss wrote: > On 8/15/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote: > >On Sat, Aug 12, 2006 at 08:14:52PM -0400, Charles Reiss wrote: > >> I wrote: > >> >It also does not allow .pmc files to overide the default idea of > >> >whether a vtable method is read-only. > >> > >> This remains unresolved though I'm not certain it should be allowed. > >> The hard part of doing it correctly is handling inheritance. > > > >It's an interface guarantee, and as such I think it's OK that it can't be > >overridden in a derived class. Agree? > > Er, when I first read that I thought you meant that with respect to > the inheritance issue, but reading again I'm not sure. Yes, that's what I meant. > But, anyways, looking over pmc2c I found that doing it 'properly' was not > too difficult, so I've done that (read/writeness is inherited by default > and can be overridden). Works For Me, thanks. > I provide the feature in the hope that people will think really hard > before using it to violate interface guarantees. Big friendly warnings are the right first step. If people start ignoring the signs and wandering onto the live minefields, we'll have to start thinking about audio warnings and fierce guards with pointed sticks. -- Chip Salzenberg <[EMAIL PROTECTED]>
