Sending again : apologies if you see this twice.

 From: Paulo Gaspar [mailto:[EMAIL PROTECTED]]
 >
 > Then "ReferenceInsertionEventHandler.referenceInsert()" keeps
 > its name?
 >
 >
 > I am making this remark because I suggested renaming it to:
 >   "ReferenceRenderEventHandler.referenceRender()"
 >
 > and you answer was
 > > That's good too - I think that the 'Insert' came from the notion of
 > > 'inserting' into the output stream.
 >
 >
 > Of course that I prefer the name I suggested (I think it is less
 > ambiguous), but I can take a conscious "no" too. I just want to make
 > sure that you didn't just forget it. (Your well fundamented NO's are
 > usually quite ok with me.)
 >

 I guess I kinda threw up my hands and said 'Feh!', or something like that.

 I figured that the NullSetEventHandler method was downright confusing, as
 you pointed out, so that warranted a change.

 As to the other, since referenceInsert() was suggested by Leon, the first
person to implement and test, and it does make some kind of semantic sense -
called when a reference value is about to be inserted into the output
stream - and no one but us seems to care, I left it.

If we get other howls of protest, then I think we still can change it before
v1.1 goes 'gold'...

geir


Reply via email to