Re: [PATCH v3 01/11] replace: forbid replacing an object with one of a different type

2013-09-01 Thread Philip Oakley
From: "Christian Couder" From: "Philip Oakley" Sorry for not replying earlier in the series. From: "Christian Couder" Users replacing an object with one of a different type were not prevented to do so, even if it was obvious, and stated in the doc, that bad things would result from doing t

Re: [PATCH v3 01/11] replace: forbid replacing an object with one of a different type

2013-09-01 Thread Christian Couder
From: "Philip Oakley" > > Sorry for not replying earlier in the series. > > From: "Christian Couder" >> Users replacing an object with one of a different type were not >> prevented to do so, even if it was obvious, and stated in the doc, >> that bad things would result from doing that. >> >> To

Re: [PATCH v3 01/11] replace: forbid replacing an object with one of a different type

2013-08-31 Thread Philip Oakley
Sorry for not replying earlier in the series. From: "Christian Couder" Users replacing an object with one of a different type were not prevented to do so, even if it was obvious, and stated in the doc, that bad things would result from doing that. To avoid mistakes, it is better to just forbid

[PATCH v3 01/11] replace: forbid replacing an object with one of a different type

2013-08-31 Thread Christian Couder
Users replacing an object with one of a different type were not prevented to do so, even if it was obvious, and stated in the doc, that bad things would result from doing that. To avoid mistakes, it is better to just forbid that though. If one object is replaced with one of a different type, the