Roger Cigol

@Der schöne Günther Please accept my apologies! @Remy Lebeau Many thanks for your wisdom here - I've learnt something new!

I am not sure that posting code that doesn't compile is very helpful unless it is absolutely clear that it is meant in humour. Incidentally I am not sure how I feel about myself but I definitely love C++ (whilst conceding that it does have it's drawbacks).

Whilst agreeing totally with @Lars FosdalI am puzzled by your reaction. It is clear that every posting you received was aimed at helping / educating you. I can't see any sign of anyone being patronising. I like to think that all the many experienced developers that look at Delphi-Praxis are understanding of less experienced folk who are trying to learn. Please continue to ask questions. Be patient if you don't always get a simple answer and check that you have expressed your question in as clear as way as you can.

This is good advice (more accurately: this is essential). But the example you give is in Delphi / Pascal rather than C++ so perhaps not entirely suited for the original question posed by a relative newcomer to C++.

This is correct.

If you add a unit then the IDE adds both the *.cpp and .h files. There can be cases where you have a .h file with no associated *.cpp file (and this is therefore not what the IDE calls a unit). In this case you can right click on the project name (= the exe file) in the project tree view and select add existing and navigate to the *.h file you want to add.

PCH = pre compiled header. It's a file created at a full build by the compiler with the pure aim of speeding up compilation. In almost all cases you can just ignore it and let the compiler delete/recreate it as it needs to.

To get any chance of an answer you need to post some code that behaves differently between two versions. Also check which compiler and target (win32 or 64bit) you are using in each case.

I think this sounds like the "auto complete" calculating what to allow you to enter as part of the code. This was a bit flakey on some of the recent versions but works quite well on 12.2

Can you paste the contents of the dfm definition of the form here for the FDQuery where the parameter :increment is defined and used. One way of doing this is to go to the form designer, select the appropriate TFDQuery component on the form, right click and select "copy" and then paste it into your Dephi-Praxis post....

Modern versions of PostgreSQL are only available in 64bit architecture. The RAD Studio IDE is a 32 bit application. It is not possible to interface to the modern postgreSQL at design time using the IDE. I have seen examples of people using an old version of the postgreSQL interface dll (a 32 bit version) to talk to modern version of PostgreSQL server. It may work but it cannot be a "guaranteed to work" route since you are asking for a dll to be compatible with a version that wasn't written at the time the dll was created. I've never wasted time trying to get this to work.

I use parameters in my TFDQuery with PostgreSQL 13 database all the time. No problems. You need to post more information in order for the community here to be able to help.

Not sure about this. It's empty when you first start windows. But as soon as you start using the clip board with any application Windows does maintain a history and WinKey+V does allow you to choose. However I don't know a way of accessing these values programatically. But that doesn't mean there isn't a way.....

It's a definite personal strength to be aware of one's own weaknesses...

I've brought a few "Classic" 32 bit VCL apps over to "Clang32". Most of the issues are related to poor code by me (often code that I wrote 30 years ago and would definitely not write now!). So in this sense whilst it is an inconvenience it is actually a good thing - it is making the code base more reliable and more maintainable. Of course I don't know what your apps do and what 3rd party components they use so the same experience may or may not apply in your case. Equally I have one set of code that is still a significant source of income for me that is based on "Classic" (again 32bit VCL). With this one I am just starting to look at changing over straight to a 64bit app using the "modern" clang64 tool set. I think I am saying (!!) that you just need to give it a go and see how you get on. You'll know within a day or two whether it's a mamouth task or a relatively straightforward one.