Leaderboard

The venerable Delphi IDE extension GExperts is about to undergo a revolutionary transformation, with plans announced to completely rewrite it using artificial intelligence and simultaneously port it to COBOL. This unexpected development marks a significant shift for a tool that has been a staple in the Delphi programming community for decades. The AI Rewrite: Starting Now The development team has just announced their decision to leverage artificial intelligence for the rewrite after facing increasing challenges maintaining the extensive codebase. What’s remarkable is the anticipated timeline – the team expects the entire process to take only a few hours once it begins. This unprecedented speed is attributed to advancements in AI code transformation technology. The AI system will analyze the entire GExperts source code, understanding its purpose, functionality, and even the quirks that make it uniquely useful to Delphi developers – all in a fraction of the time it would take human developers. Why COBOL? Perhaps the most surprising aspect of this transformation is the announced port to COBOL. This decision has raised eyebrows among the development community, as Delphi and COBOL represent dramatically different programming paradigms and eras. However, the team cites strategic reasoning behind this choice. COBOL continues to power critical systems in banking, insurance, and government sectors worldwide. This port will open GExperts to an entirely new ecosystem, potentially breathing new life into the project while serving developers maintaining legacy systems. Expected Timeline The project has not yet begun, but development is scheduled to start immediately. With the AI-powered transformation expected to take only a few hours from start to finish, the team anticipates having a functional COBOL version of GExperts available for testing within days rather than the months or years such a port would traditionally require. Looking Forward For developers interested in this innovative crossover, beta releases are expected to be available remarkably soon, with the team promising updates on the progress within the next 24 hours. This bold reinvention of GExperts, once completed, will demonstrate how established developer tools can evolve in unexpected ways, leveraging new technologies to reach broader audiences while maintaining their core value proposition. (Yes, AI is great! Even for writing April Fools jokes. Thanks to Claude.ai writing this only took a few minutes and it actually sounds like a press release some cool cloud AI blockchain outfit could have written.) Original blog post here.

Due to the continued abuse, the following functionality will change from this date: Images, links and emojis are generally disabled Text emojis will be allowed Quoting limitations will be enforced to single sentences AI filters will be applied to the posts to moderate strong language, personal attacks, and spam Lack of proper grammar, punctuation and Capitalization will be penalized Humorous comments must achieve a rating of at least 42 to be accepted as humor Cat images will be allowed on Saturdays(no nudes, i.e. cats without hair) Recursive posts will be moved to Posts, Recursive Cursive fonts will be righted Use of blinking fonts for important spam is encouraged Links to Rick Astley music videos are encouraged

After much contemplation (and asking Claude AI for advice), I'm proposing a new programming language with roots in Delphi (thus the name) but with some interesting and revolutionary ideas that will take into account concepts never before attempted in software development. Some of these ideas include syntax checking that changes based on the time of day, optimization that improves when builds are automated, and crypto-mining to lessen the cost of the IDE. Some will argue that that reporting compilation errors to social media could hurt the reputation of some programmers but I think it will incentivize them to become better (or at least more careful) programmers. What do you think? Read the full article here.

Python + DelphiVCL + VTK + VCL Styles, a great combo! A sample video of a Python program that I use to fastly check the new kinematics algorithms.

A little rude but...There was no blame assigned to anywhere except myself for not understanding.

Do you see any other people coming back onto your post here? They've washed their hands of you. You are arrogant and disrespectful towards those that are giving their time without compensation and you have only insulted everyone here. Whats the point of having thread-unsafe code?

https://stackoverflow.com/questions/16150218/is-it-possible-to-create-a-type-alias-to-a-generic-record-in-delphi https://stackoverflow.com/questions/10060009/is-it-possible-to-create-a-type-alias-to-a-generic-class

Oh, I was not aware, that it is yours I am even more thankful then! Have you tested the behaviour with a mobile app for general usage?

Thank you, but I am confident in using AI for the conversion. I'll call Elon Musk at DOGE for advice if necessary.

Hey David. I was pointed to this by one of our customers and was wondering if you can provide more info please. This was from 2020, but we do think that pdata is handled correctly, specifically because we do have one case of C++ code with pdata and exception info, designed to throw SEH exceptions via RaiseException as part of its functionality, working correctly statically linked into Delphi code (that's the delay-loading code.) Maybe it's an xdata issue (unwind info)? So what you describe could be very true -- Delphi doesn't do exceptions quite the same as C++, and it gets complex, and x86 uses SJLJ, and... -- but our engineers are still puzzled trying to understand the exact situation. We'd love to hear more info on the scenario! Oh -- and I should note that I am far from an expert on this. It is likely that first paragraph has technical mistakes. They will be entirely mine. I can even arrange a call with one of our engineers directly if you'd like! That way you can skip the middle-man, me 😉 Please email david.millington@embarcadero.com. These days we have bcc64c / Modern and that should be a great compiler so if you are building C++ on Win64 please use that one 🙂

And her sister came 42nd in a county beauty pageant.

COBOL - Completely Obfuscated Business Orientated Language... 😉

Actually WPARAM is Unsigned

There is actually a connection between COBOLand Delphi: The company formerly known as Borland, who originally developed Delphi, was sold to Microfocus after spinning off the development tools to CodeGear. Microfocus was well known for Microfocus COBOL, which nowadays is called Visual COBOL and possibly includes some technologies Microfocus acquired in this process. But the real reason I came up with COBOL was the announced intention of DOGE to port the COBOL software to Java using AI in just a few months. So, if they succeed, we can expect to easily port the COBOL version of GExperts to Java.

No, it looks like you don't understand multithreaded development at all if you're suggesting using critical sections. If you put critical sections and threads have to wait for each other every time, what's the point of using threads then?

This is the style that pasfmt uses. It's most consistent to break after every visibility specifier because it does start a new section, and there may not be a visibility specifier before the next section: type TClass = class(TObject) private const SomeConstant = 5; type SomeType = integer; end;

I can't answer your question. But an alternative approach would be to create your own dialog however you want, and then write your own class that implements the IFMXDialogServiceAsync interface to show your dialog, and then register that class with FMX using TPlatformServices.Current.AddPlatformService() (be sure to unregister the default implementation using TPlatformServices.Current.RemovePlatformService() first).

I think more consistent with Embarcadero style will be following, since there could be multiple consts/types/vars TClass = class(TObject) private FSomeField: integer; private const SomeConstant = 5; SomeOtherConstant = 6; private type SomeType = integer; SomeOtheType = string; private class var SomeClassVar: integer; SomeOtherClassVar: string; end;

You are using the version of FormatDateTime() that relies on global variables initialized with your PC's locale settings. For instance, the '/' specifier is not a literal slash character, it is a placeholder that uses the global DateSeparator variable in the SysUtils unit. This is documented behavior. You can update those globals to customize things like the date/time separators, but this affects the whole app, and is not thread-safe. When you need custom formatting that is locale-agnostic, you should use the version of FormatDateTime() that takes a TFormatSettings parameter, eg: procedure TForm1.Button1Click(Sender: TObject); var lDate: TDateTime; lFmt: TFormatSettings; begin lFmt := TFormatSettings.Create; lFmt.DateSeparator := '/'; lDate := EncodeDate(2025, 3, 26); Edit1.Text := FormatDateTime('dd/mm/yyyy', lDate, lFmt); end; The alternative is to wrap desired literal text with quotes in your format string, eg: procedure TForm1.Button1Click(Sender: TObject); var lDate: TDateTime; begin lDate := EncodeDate(2025, 3, 26); Edit1.Text := FormatDateTime('dd"/"mm"/"yyyy', lDate); end;

David Millington pointed me to a solution, through the support of Embarcadero: This solved the problem for me.

"RTC SDK was originally developed by Danijel Tkalčec in 2004, and acquired by Teppi Technology in 2018 . Now, as of May 20th 2022, we announce that ReatlThinClient SDK (a.k.a. RTC SDK) is open source." https://rtc.teppi.net/ https://github.com/teppicom/RealThinClient-SDK