Re: explicit destruction and placement new

2004-11-23 Thread Martin Vermeer
On Tue, 2004-11-23 at 18:49, Andreas Vox wrote: > I think all of us would like to have a shiny, bugfree 1.4 release of LyX > as soon as possible (say for Christmas), but currently it looks as if there's > not enough man power to reach that goal. Actually it looks a lot better already than just

Re: explicit destruction and placement new

2004-11-23 Thread Lars Gullik Bjønnes
Andreas Vox <[EMAIL PROTECTED]> writes: | I don't know if you two get along when drinking beer or if you are sitting | at opposite ends of the table then also, beer bottles are nice blunt instruments. We actually get a long pretty well. | but it surely gives bad vibrations | to read posts lik

Re: explicit destruction and placement new

2004-11-23 Thread Angus Leeming
Andreas Vox wrote: > I don't know if you two get along when drinking beer or if you are > sitting at opposite ends of the table then also, but it surely gives > bad vibrations to read posts like this on the list. When drinking beer they seem to get on fine, so long as they are both at the same en

Re: explicit destruction and placement new

2004-11-23 Thread Andreas Vox
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes: < Andre Poenitz <[EMAIL PROTECTED]> writes: < < | To be even more blunt: This kind of work does not help us to get 1.4.0 < | out of the door. The small good it does is outweighed by distracting < | people as seen e.g. in the XML discussion. <

Re: explicit destruction and placement new

2004-11-22 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | To be even more blunt: This kind of work does not help us to get 1.4.0 | out of the door. The small good it does is outweighed by distracting | people as seen e.g. in the XML discussion. Just to out-blunt you: I am not allowing you to command what _I_ d

Re: explicit destruction and placement new

2004-11-22 Thread Andre Poenitz
On Mon, Nov 22, 2004 at 09:34:32PM +0100, Lars Gullik Bjønnes wrote: > >>this->~SomeClass(); > >>new (this) SomeClass(foo); > >> > >> Does this work as intended? Or am I just way off? > > > | Maybe. > > I just had a look in my books and Mr. Sutter calls this the > "anti-idom" and says to

Re: explicit destruction and placement new

2004-11-22 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | On Mon, Nov 22, 2004 at 12:33:23PM +0100, Lars Gullik Bjønnes wrote: >> >> I am trying to make the inset hierarchy more immune to splicing and >> wrong usage. >> >> In mathed this construct is used >> >>*this = SomeClass(foo); > | Where? In fact,

Re: explicit destruction and placement new

2004-11-22 Thread Kuba Ober
On poniedziaÅek 22 listopad 2004 01:26 pm, Andre Poenitz wrote: > On Mon, Nov 22, 2004 at 12:33:23PM +0100, Lars Gullik BjÃnnes wrote: > > I am trying to make the inset hierarchy more immune to splicing and > > wrong usage. > > > > In mathed this construct is used > > > >*this = SomeClass(foo);

Re: explicit destruction and placement new

2004-11-22 Thread Andre Poenitz
On Mon, Nov 22, 2004 at 12:33:23PM +0100, Lars Gullik Bjønnes wrote: > > I am trying to make the inset hierarchy more immune to splicing and > wrong usage. > > In mathed this construct is used > >*this = SomeClass(foo); Where? In fact, if this is Cursor/DocIterator code which retains anchor

explicit destruction and placement new

2004-11-22 Thread Lars Gullik Bjønnes
I am trying to make the inset hierarchy more immune to splicing and wrong usage. In mathed this construct is used *this = SomeClass(foo); (or the variant this->operator(SomeClass(foo)) ) My method of avoiding splicing and wrong usage does not like this very much... so I have replaced this w