Attila Kovacs

@Kas Ob. I went through all these versions in my mind, even with clearing in the class operators, but it's just not right. You also have to know the implementation details for that version. @Marat1961 There is no desire on reinventing the wheel, I would have been pleased if there were something in the RTL. The cited func works with path separators and not url separators, as far as I can see. However the suggestion by @Kryvich to introduce a TURIPart=type string; and add some helpers sounds good.

@Kryvich I'll think about #2, sounds legit. thx

@Kryvich Yes, but It's slightly different from my wishes. Dir1 Dir2 has to be TURL.

I'm using A and O. And I can write it down by my own.

He wants to _find_ the appropriate enum and not obfuscate it deeper. It should be a task for the IDE which fail big time in it, even the help provided by emba is trying to hide which are the possible values. Still, I would not say that your example is a "better way" but you are mixing variables with types. So it should be something like: type TGEnums = class type THTMLType = (htTemplate, htStatic, htHeader, htCustom); end; var x: TGEnums.THTMLType; begin x := TGEnums.THTMLType.htTemplate; --- or --- type THTMLType = (htTemplate, htStatic, htHeader, htCustom); TGEnums = class type HTMLType = THTMLType; end; var x: THTMLType; begin x := TGEnums.HTMLType.htTemplate;

I just felt like with the best cow of the dairy-farm which gives 40 liters of milk then knocks over the bucket. Can't compile the code because of the inline variables 😕

Well, maybe you could write a generic search class having the whole code only once in your app, but hard to give any advice without knowing the details. Just leave it as it is, it always works.

move the loop into the inlinded proc

Register optimization, I never put more than one test into one procedure, but the problem is the inlining introduce the extra boolean evaluation instead of just the 3 in the "if". 🤷‍♂️

change the order of the 2 loops and give us the new results

looks like "TsgList<T> = record" should be "TsgList<T: record> = record"

There was a problem with the Compile Dialog as it was refreshed too frequently and since it's also themed it was very slow. I can't find anything anymore regarding this issue, maybe it has been solved since, but it's easy to check if you disable the dialog and measure the compile time. AFAIR IdeFixPack was targeting this problem too.

there is also https://www.componentace.com/bde_replacement_database_delphi_absolute_database.htm

There are bunch of "endless loop" hits on zlib from 2015, the one in RTL has a date from 2014, maybe you should re-compress the original data and see if it happens again. That would also make others satisfied when you switch to another lib. Eventually try to decompress it with more recent zlib version. https://unix.stackexchange.com/questions/22834/how-to-uncompress-zlib-data-in-unix It would be cool to know the results.

Ctrl+# is the toggle comment menuitem on the editors context menu in the german IDE, not sure though if it has anything to do with whatever it is, but I'm sure you already checked where this "Sender" belongs to.

It is no coincidence that checksums were invented.

Unless it's a trial and triumph.

a swallowed windows message like button down / up, usually when you manipulate the focus inside events, for example

Nope, it has nothing to do with santiago's except the idea is stolen. It's a working plugin without any OTA conventions so it's ugly and would be harder to maintain. But the OTA is somewhat limited to get this plugin thin and versatile, so I had to go this way. Also, getting the breakpoint list from Parnassus depends on code which was bought by emba and gone under without a ripple. 😞

@Dinar It's not just me! 😉 Well, then just press Ctrl+Alt+ArrowUp or Down 😉

@Dinar :)) Sorry, looks like I'm in write only mode 🙂

As an alternative:

@Lars Fosdal I heard that several times and I still can't imagine why not a middle tier, why sp's?

O R M

Mind the declaration of those helper routines. The ones needing a parameter are for sure class methods, thus they will as work with aStr.xyz() as with String.xyz(); In this case the ToLower is non-class method, LowerCase is. Now if you wonder why are they called differently, try boolean.ToString(True); and once you found out what is happening try not to scream.