Leaderboard

All this drivel that happens every time when David and Rudy collide is rather annoying to me and totally went off topic long ago. But that's what you can ignore content for. I would appreciate if you as a mod would cut that out and move it to it's own thread.

The newest development snapshot should fix this bug. http://andy.jgknet.de/fixpack/dev

That's why I restrict those paths to the Delphi ones. For any library used in a project there will be a search path entry in the project file. Unfortunately some library vendors or maintainers sacrifice the minimalism of these global search paths for the simplicity of their setup experience.

Ok ok ok...just try to get back to the topic at hand... which is...um... "Rapid generics"

So the idea is simply to get a list of all units linked into the project? That can be done by parsing the map file, if one is being created. And that's a lot easier and faster.

Ref. paths and VCS systems... We use standard paths C:\SomeFolder\Projects Common ThisCollection ThatCollection External Lib1 Lib2 Proj1 Proj2 We also use a $BIN environment var to direct the project outputs. Allows the team members great freedom for where to put their source, and where to direct the output. and try to ensure that all project search or include paths are on this form ..\Common\ThisCollection Those are stored in the .dproj which can be committed to the VCS. That also allows me to check out various versions Projects <- my typical working branch switched between trunk/pilot/live Projects.Rio <- while still on Tokyo, but testing Rio Projects.Trunk Projects.Pilot Projects.Live

Somewhat off topic, but related. Ctr+-F12 gives you a list of units to open, and I assumed it was from the search paths and project paths, Turns out that it also will look at the .dpr uses statement. Ideally, the paths should be relative... uses SomeUnit in '..\RelativeFolder\SomeUnit.pas' But, I had a stale test project in my project group where the uses path used an explicit path uses SomeUnit in 'c:\Obsolete.Path\to\RelativeFolder\SomeUnit.pas' So, pressing Ctrl+F12 gave me both of these - even if Obsolete.Path didn't exist.

HKLM\Software\WOW6432Node\Embarcadero\BDS\<version>\Library\* and a copy for each user under HKCU\Software\Embarcadero\BDS\<version>\Library\* The latter is the one edited in the Tools -> Options dialog.

Please don't hijack the conversation to offtopic.

True years ago, but these days not so. Just put some code through godbolt and marvel at the code that it generates. You don't have to get that complicated before you see the compiler spotting optimisations that are very far from obvious. Optimisers now have deep knowledge of hardware architecture and can use that to make choices that are beyond almost all human asm programmers.

If your Note 8 has Oreo 8.0 OS then debugging does not work because Google screwed up on OS level. You need to update OS to 8.1 that fixes the issue. It was not something EMBT could fix. http://blog.marcocantu.com/blog/2017-december-delphi-android81-debugging.html

It's my own. You can get it here: http://melander.dk/download/ResourceEditor20190309a.zip