On Mon, 29 Aug 2022, James Richters via fpc-pascal wrote:
Thanks for the discussion everyone, it does shed some light on what's
going on. I agree it would be impossible to change it now, It was
actually a GREAT idea to make it customizable, and that serves my needs
just fine. I guess all
Thanks for the discussion everyone, it does shed some light on what's going on.
I agree it would be impossible to change it now, It was actually a GREAT idea
to make it customizable, and that serves my needs just fine.
I guess all that's left is to update the documentation to show what it
On 8/29/22 11:33, Jean SUZINEAU via fpc-pascal wrote:
Le 29/08/2022 à 01:41, James Richters via fpc-pascal a écrit :
If a special function is needed for some COM thing or weird Winapi
thing, then that function should be part of the unit that needs it,
not modifying the generic function
Le 29/08/2022 à 01:41, James Richters via fpc-pascal a écrit :
If a special function is needed for some COM thing or weird Winapi thing, then
that function should be part of the unit that needs it, not modifying the
generic function intended to be used for general purpose applications output
On Sun, 28 Aug 2022, James Richters via fpc-pascal wrote:
I'm curious if there is a way to search the FPC version history of changes
for BoolToStr to see why it was changed, and see if there is a valid
reason not to change it back. it was obviously changed from the way the
documentations is
