On Thu, Nov 19, 2009 at 20:46, Jonas Maebe <jonas.ma...@elis.ugent.be> wrote: > > On 19 Nov 2009, at 11:42, Alexander Klenin wrote: > >> No, I asked for an example of code that would be negatively affected by >> changing "var" to "out" in FillChar parameter. > > I don't know by heart anymore, but as I mentioned the compiler crashed when > I tried that (or if you did that move, which has the same problem). There is > probably rtl or generated initialisation code that depends on the current > semantics of move/fillchar).
So, we are unable to fix FillChar because it would uncover bugs hiding in the other places? ;-) Ok, so how about introducing, say, FillMem procedure, which is identical to FillChar except that it has "out" parameter, and deprecation of FillChar? I always thought that "FillChar" name is somewhat misleading anyway, so this is a good opportunity to change it. -- Alexander S. Klenin _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
