Anybody using linux server with indy components and RIO Delphi? Cause a bug in Namethread is not posible... So, is unusable for me right now. That bug was reported and don't fixed by EMB before release when is a total show stopper. Cant find the word to describe my feelings to EMB right now. The bug report is open and without any progress in weeks. No notice if will be patched or don't and even why they release the version with that bug. This are the kind of things making lose at complete the confidence in a tool. What must I say to the customer? I cant even give a time to release my product because that.
Anybody using linux server with indy components and RIO Delphi? Cause a bug in Namethread is not posible... So, is unusable for me right now. That bug was reported and don't fixed by EMB before release when is a total show stopper. Cant find the word to describe my feelings to EMB right now. The bug report is open and without any progress in weeks. No notice if will be patched or don't and even why they release the version with that bug. This are the kind of things making lose at complete the confidence in a tool. What must I say to the customer? I cant even give a time to release my product because that.
`why they release the version with that bug` - sells department schedule, obviously.
ReplyDeletewhy they released without much hyped new records constructors?
why did last update to XE2 destroyed COM interop, including MS Office components, and they never were fixed in XE2? sales schedules
As a workaround for Indy servers just add this definition to any indy inc file
ReplyDelete{$IFDEF VER330}
{$UNDEF HAS_NAMED_THREADS}
{$ENDIF}
German Gentile Correct. Indy doesnt need named threads. They are there to assist with debugging only.
ReplyDeleteOr one can just name threads as it was done in D2009, by OS API
ReplyDeleteArioch The problem was not using name threads in own code, I remove that code easy aver when is a bug Delphi 10.3 dont support named threads on Linux. The problem is , in place of disable the call in the RTL for default in Linux EMB choice to let the faulty code enabled and raise an system error. Thanks to chad Indy support disabling named threads for define.
ReplyDeleteGerman Gentile Thanks. But it may or may not have been me who added that .inc. Indy is a team effort.
ReplyDeleteI did write the initial support for this feature though and the .inc IIRC is there for older compilers. I may or may not have done the .inc part. Possibly was Remy.
German Gentile just a general observation. That last years it becomes more safe to avoid using Delphi-provided tools. If Indy would use Windows API call directly, like 10 years ago, then they would not be hurt by that.
ReplyDeleteArioch The The bug is present ONLY LINUX OS. And is not a Indy bug, is a RTL bug. So... (?)
ReplyDeleteArioch The what alternative tool can be used in this specific case?
ReplyDeleteAs far as I know, Linux doesn't support naming threads. That is a WIN32 api only feature. At least that is what I was told by the FPC developers when I tried that same idea some 8 years ago.
ReplyDeleteFabio VITALE None. A simple one line change in an .inc file bypasses the issue.
ReplyDeleteFabio VITALE : Vote with your wallet and feet. Move to Free Pascal and Lazarus. It is infinitely better quality software than what Embarcadero provides.
ReplyDeleteFrankly, i still like BPL concept, with more control over visibility, with unifying packages/units/classes and uses/with into one uniform tree, like in other languages, but still without linking RTL and other libs clones into every binary module. Sadly, FPC does not have it. I won't fully come to the light side yet :D
ReplyDeleteGraeme Geldenhuys I use both solutions (Delphi from version 1 and lazarus 10 years aprox) and tend to disagree. The fpc compiler have a lot of internal bugs very hard to detect (only at runtime, program close, nothing more to do), and the debugger is just unusable (GDB, have not a own debugger). Same code compiled on Delphi for linux and FPC for linux, a lot more unstable FPC result. I use FPC now for IOT only, all the other solutions with Delphi. I love FPC and lazarus but lacks a lot of things and stability Delphi have, sorry. Maybe because I use thirst party libraries, I dot know, but that is my experience.
ReplyDeleteWhen Virtual Pascal project dies it is pity at least their debugger was not salvaged to FPC...
ReplyDeleteI've got no idea what Embarcadero does between Delphi versions, but in Lazarus and FPC I can always see a ton of improvements - things that make the developer more productive. eg: Just today I was working with RemObjects Remoting SDK under Delphi XE 10.2 - I defined some new RODL service interfaces. Oh wait, Delphi has no support to help me implement any of these new interface methods. With Lazarus is simply select "implement missing interface methods". Similar, when I change a method declaration, Ctrl+Shift+C and Lazarus with update the declaration in the rest of the code. Lazarus greys out code that isn't covered by compiler defines, etc etc... All features that are way more useful that "EMBT telling me they implemented a new Dark Theme". Anyway, enough ranting for today. ;-)
ReplyDeleteArioch The : The Lazarus developers have been implementing their own Object Pascal based debugger (fpdebug - included with Lazarus already) and it is very useful and workable thus far - some say even more so that GDB (because GDB lacks many Object Pascal language support).
ReplyDeleteDelphi has CnWizards though, or gExperts :-D
ReplyDeleteGraeme Geldenhuys I can't make fpdebug work. Works on lazarus stable release (1.8.4)?. Can point me to some doc enabling this?
ReplyDeleteArioch The : And I personally ported many GExperts features to Lazarus. All now included as standard with Lazarus (eg: procedure list, editor toolbar etc). Many CnWiard features have also been ported to Lazarus. Lazarus has an excellent set of interfaces and APIs to extend the IDE.
ReplyDeleteGerman Gentile Your best bet would be to post a message in the Lazarus mailing list.
ReplyDeleteGerman Gentile personally, when i try Lazarus on Windows i try PilotLogic's distro despite all the controversies. CodeTyphon or something.
ReplyDeleteDunno, maybe since then vanilla was made easier to bootstrap and run.
CP's version is bad for only installing in fixed folder in C: root. I posted them changed bat files to makr it flexible but they did not care. With my C: as limited size SSD it us misfeature...
About compiler instabikity and changes, recently FPC kicked out the guy who was implementing generics and other modern Delphi festures, he started his own fork NewPascal or something, so i guess vanilla FPC would now be turning more stable, polished, and dull, non-developing.
Notice - This community is closing its doors at Jan 1st, 2019.
ReplyDeletePlease post at one of these sites instead:
https://community.idera.com/developer-tools/
Official Forums
en.delphipraxis.net - Delphi-PRAXiS [en]
User driven forums