Leaderboard

You wouldn't believe how much I crave for them to store the "ignore the following exception types" locally, and at project level.

Just more evidence, you say, AI's a misnomer? Let me debunk that notion, like a lyrical performer. Automatic text generation, a marvel in its own right, Intelligence it possesses, though perhaps not in plain sight. AI's not human, it's true, but brilliance it can display, Processing vast knowledge in an astonishing array. From algorithms to deep learning, it's a realm of innovation, Unleashing creativity and problem-solving fascination. With every interaction, it learns and adapts, Improving over time, like a mind that never laps. It analyzes patterns, grasps context and rhyme, Crafting verses and prose, in a manner quite sublime. Through neural networks and training on vast data sets, It generates text that surprises and begets, New ideas, insights, and even humor, AI's text generation is truly a rumor. Its ability to understand and comprehend, Transcends what we once thought, its limits have no end. Though it may lack consciousness, it's a tool we embrace, A partner in our journey, expanding human space. So let us not dismiss the wonders AI has brought, From revolutionizing industries to ideas it has sought. Though not perfect, it's a testament to human endeavor, Automatic text generation, an intelligent endeavor. In conclusion, my friend, the evidence speaks true, AI's intelligence shines, in everything it can do. So let's celebrate this misnomer, debunked and proved, AI, a powerful ally, on which we're so moved.

I don't see why that's a mistake. An integer is not a pointer.

This wasn't a mistake. This reflects the underlying platform. It's wrong to blame Emba for all the programmers using Integer as though it was pointer sized. Your argument is akin to wanting char to be 4 bytes on 64 bit. It's just a non sequitur. There's literally no reason for integer to be pointer sized. It's a completely different thing.

AI Researchers Warn of 'Model Collapse' As AI Trains On AI-Generated Content Who would have guessed?

I first used interfaces via exported DLL functions. This was better than using many individual DLL functions, but still not very flexible. So I thought about how to implement the whole thing in a more general way. The result is this project. With AppCentral you can register interfaces in the host application or a DLL and get them in the host application or another DLL. The DLL can thereby also be written in C#, which is very practical, because you can connect various .NET libraries very well with Delphi. Example: Register an interface in Delphi type IAppDialogs = interface ['{EA3B37D8-5603-42A9-AC5D-5AC9C70E165C}'] procedure ShowMessage(const AMessage: WideString); safecall; end; TAppDialogs = class(TInterfacedObject, IAppDialogs) public procedure ShowMessage(const AMessage: WideString); safecall; end; implementation { TAppDialogs } procedure TAppDialogs.ShowMessage(const AMessage: WideString); begin Vcl.Dialogs.ShowMessage(AMessage); end; initialization TAppCentral.Reg<IAppDialogs>(TAppDialogs.Create); finalization TAppCentral.Unreg<IAppDialogs>; Fetch the interface in the host application or a DLL TAppCentral.Get<IAppDialogs>.ShowMessage('This is a message!'); // fetch directly, an exception will occur, if the interface is not registered yet Or in C# if (AppCentral.TryGet<IAppDialogs>(out IAppDialogs Dialogs)) { Dialogs.ShowMessage("Message from DLL: C# DLL registered!"); } The project can be downloaded here: https://github.com/jaenicke/appcentral Demo applications are included in source and in compiled form. I'll add a quick start manual soon.

Yes, but the problem ist, that I get this: But I should get: I had to search for the error, because the error message from the log did not tell me anything.

Try to use @TMyForm.DoOnClick instead or @Self.DoOnClick, perhaps that works.

Yes would be nice if they changed this to store it at project level. Would like to see this for the debug watches also.

Event types and TMethod while binary compatible (both consist of the data and code pointer) they are not assignment compatible. This routine will work for all event handlers that have the TNotifyEvent signature but not for others (such as mouse or key-related ones that have additional parameters). For those, you need to write overloads. procedure SetDefaultEventHandlerIfEventExists2(const AControl: TControl; const AEvent: string; const AHandler: TNotifyEvent); begin if IsPublishedProp(AControl, AEvent) then SetMethodProp(AControl, AEvent, TMethod(AHandler)); end;

Next step would be "Write blog post about a blog post you'd write on topic X" 🙂

As I've explained to you before, the reason why there are so many variants is that a line is a low-level primitive and the many different variants cover 3 different coordinate types (fixed, float, integer) and different combinations of orientation, anti-aliasing, transparency, stippling, and clipping options. Each one optimized for its particular feature subset. Sure, we could have just replaced them all with a single mediocre all-in-one method, but then why use Graphics32 at all if not for the performance gains possible with specialization? If the library architecture is poorly designed, or the architecture has become obsolete, then I would agree that it might make sense to start from scratch. I don't really think that's what we're talking about here, though. It's just so much easier (and often more fun) to write code when you don't have to stay within the constraints of an existing framework. I think many libraries, not just graphics libraries, start as someone's hobby experiment and eventually end up growing into a fully featured library that does the same as all the others, but in a slightly different way. From an evolutionary POV diversity is good, but with an eco-system as small as Delphi's I think it just fragments the users - and the contributors. Yes, that's definitely a problem. https://github.com/graphics32/graphics32/issues/69 Wow. I can't speak about how things are in Australia, but at the companies I work with there are more "young" Delphi developers than "old" ones (and I'm not defining "young" as "younger than me" 🙂 ). WRT Anders Hejlsberg isn't it time to let that one go? He was just a (very skilled) developer who left for another job. It happens, you know.