In fact it will use the last one that was found and fwiw this is imo bad and error prone behavior - I guess everyone has had that happen at least once that with some version change or update of some code some clash happened - especially when a routine with the same name but different parameters was introduced somewhere.
I had the impression you are aiming for the best possible solution for a new feature so I brought this up - if you are happy with a "better than before" then please go for it. > On 13 May 2019 at 13:51 "Marcos Douglas B. Santos" <m...@delfire.net > mailto:m...@delfire.net > wrote: > > > On Mon, May 13, 2019 at 7:09 AM Ondrej Pokorny <laza...@kluug.net > mailto:laza...@kluug.net > wrote: > > > > > > On 13.05.2019 11:59, Stefan Glienke wrote: > > > > > > > When I wrote "existing code" I was referring to the > > future when people turn this on for their code and then helpers get changed > > and not "today existing code". > > > > > > > > The problem is the same with old style Delphi-like helpers. > > > Multihelpers > > didn't change much in this regard. > > > > > +1 > This is the same as having two functions, with the same signature, in > two different units. > Your program will use the first that was found. > > regards, > Marcos Douglas > _______________________________________________ > fpc-devel maillist - fpc-devel@lists.freepascal.org > mailto:fpc-devel@lists.freepascal.org > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel > _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
