Leaderboard

Since December Stack Overflow and other sites in the network have been spammed with AI generated answers which are usually incorrect while sounding plausible. To handle this problem moderators working with other users and Stack Overflow staff enacted the policy that bans all AI generated posts. Such posts are deleted and users can be suspended (usually for a week) for posting them. To get the better picture about the impact, we are talking about thousands of users and even more posts. See: https://meta.stackoverflow.com/questions/421831/temporary-policy-chatgpt-is-banned However, last week the company enacted another policy which still allows moderators to moderate AI generated content, but effectively does not allow them to to use any means necessary for detecting such posts. In other words they can remove posts mostly if user admits post is AI generated. Allowing AI posts on sites will effectively kill the sites and elected moderators have decided to take an action and go on strike, along with other users of Stack Overflow and other sites in the stack Exchange network. Strike is scheduled to start tomorrow on Monday, Jun, 5th. Unofficial announcement of strike on Stack Overflow (there will be another announcement on the main Meta tomorrow) https://meta.stackoverflow.com/questions/424979/what-has-happened-to-lead-moderators-to-consider-striking If you have Stack Overflow or other Stack Exchange account please support the strike and sign the strike letter at https://openletter.mousetail.nl/ Signing is made by automatic authentication with Stack Exchange network account through browser if you decide to sign. You will have to enter display name you want to be displayed on the letter as some people have different display names on different sites. Thanks!

Added to LLVM sort library it seems. https://www.nature.com/articles/s41586-023-06004-9 https://github.com/deepmind/alphadev -Tee-

The problem is that all variants of IGenericList<T> have same GUID so Supports function will succeed even though those different generic lists are not compatible.

There is not bug in compiler, but in your code. When you say LCastedList.Add(TAncestorObject.Create) What will happen is equivalent of following code: var Tmp: IInterface := TAncestorObject.Create; LCastedList.Add(Tmp); This will be because LCastedList is declared as IGenericList<IInterface> and stores IInterface references. However when you retrieve stored reference you will call that on original list which is declared as IGenericList<IAncestorObject> and retrieved reference will be of type IAncestorObject and you can try to call LObj.ID on that retrieved reference. But in reality stored reference was IInterface, not IAncestorObject and it crashes when you call ID on it because that method (GetID) it simply does not exist there. Point of generics is that you have same type stored in the background, not to store incompatible types. even though there is same object behind those two interface references, those interfaces are completely different types represent different entry points to that object. Sometimes you can force "wrong" type to be stored at runtime, which is usually not what you should be doing, but if you do, you need to make sure that every time you retrieve something that might be "wrong" you cast it back to appropriate type. var LTmp := LList.First; var LObj: IAncestorObject; if Supports(LTmp, IAncestorObject, LObj) then var LID := LObj.ID ;

There are plenty of places where this "terrible" looks like Heavens

static (ie, 'class' methods) cannot access members since they don't refer to any instance of an object. You seem to be conflating a Factory pattern with ... a mess (?) Are you wanting a Singleton here? i can't really tell what you're trying to accomplish. Try explaining it in words first because your code makes no sense to me.

That depends on where you live and how you file your taxes (joint? single?), and how many children you have. If your salary is 100k a year, the employer cost is more like 150k. Your federal tax on 100k would be at a marginal rate of around 20% with the current tax brackets but that depends on whether you file single or joint with a spouse (and if that latter, what the combined total would be). You would also be paying 50% of your FICA taxes (social security & other entitlements). You would not "take home" more than 80k if your salary were 100k. Probably much less depending on where you live; then you pay state taxes, unless you live in a state with no income tax. There is also a standard deduction taken off your income that you won't be taxed on, etc. Anyone who thinks shifting all of this burden to employers is not thinking straight. They would not just eat these costs. Real wages would adjust to account for it. Employers already have a very high cost of employment that is not reflected in a paycheck stub. 100k a year is not what it was 30 years ago, that much is for sure.

Yeahbut, do we really need it? I want it, but the reality is that Emba dev resources are very limited. Yes yes, we should not have to choose, but, since somebody does have to choose, would you choose a 64-bit IDE project and all that entails, introducing all those new bugs that will inevitably take several releases to find out and (maybe) fix, or would you choose something else? I would not make 64-bit the priority. They still have incorrect mac header conversions they haven't dealt with despite reports. etc. I would also not make MDI support in VCL Styles a priority, as they seem to be doing now, but perhaps that goes to show, you have to have a big support account and a direct line to product management to get what you want worked on. That's just the cynic in me though. I can't imagine why someone thinks putting resources to enhancing MDI support is the way forward for Delphi, but they think it is so important they are blogging about it.

Using the debugger works for most cases. But that (memory overwrite) is exactly the kind of bug where changing some compiler options might make the problem disappear because the memory layout changes. Of course the bug would still be there and simply waiting to bite you in the back.

So, if you're in USA get $100k/yr, what real income is?

LSP is separate process and it's memory consumption does no affect the IDE. Extracting that functionality outside and reducing IDE memory footprint was one of the reasons LSP was introduced in the first place. There is known GDI handle leak in Parnassus Navigator https://quality.embarcadero.com/browse/RSP-40986 Also IDE is using a bit more GDI handles than it used to and it seems that it has some caching issues, where it caches the component icons but it does not have a cache limit and it does not release those that were not accessed in for some period of time. Opening plenty of forms and accessing many different components during design time can hit GDI handle limit. AFAIK you can increase that limit (I never had issues so I never tried it) https://stackoverflow.com/questions/38612364/how-to-increase-the-maximum-amount-of-gdi-object-for-windows-10

It's a good thing we have lawyers. Otherwise I would understand everything

My guess is different memory layout in debug and release mode. That's why the code inserted to debug changed the behaviour of the bug.

Enable range checking, at least in debug builds

Anyway you should use the debugger to inspect this. Enable debugging for the release build.

Then the error is most likely located inside that code.

Does it work when you omit doStuff?

I've gone back to an old Skype Text conversation I had about this issue. The PA Server for remote debugging did not work for 11.1 but did work for 11.2.

I stopped asking or answering questions on SO years ago due to the moderation. Life is too short to bother with the aggravation.

That would have been, and still is, illegal

Be careful what you wish for, as you may actually get it.

EUR and USD are almost equal right now. I was paid $32k back in 1982. Current salaries are around $100k, and even really cheap Delphi devs are $70k. Full stack web devs are up to $150k. Delphi is a "full-stack" tool, but nobody seems to regard it as such. 🙂

No, but that's in Europe, so you can't compare salaries easily to US salaries, even if you convert EUR to US$. Looks a bit on the low side to me too though, especially for Rome, but I am not that familiar with salaries and cost of living in Italy either.