Sherlock

That watch is a medical device, or rather it should be. Because in the end it is what the manufacturer says it is (intended use). So if you create a smart watch that monitors cardiac rhythms you have to formulate its intended use carefully. For example you might state it should be used by athletes and those who would like to be to keep an eye on their heart - then you're almost golden... almost, because you'll have to deal with foreseeable misuse, someone with a history of pathologic arrhythmia might think it clever to use this watch to warn them when something really bad happens to their heart - but since the watch or algorithms where designed with healthy users in mind it'll either alert constantly or never (I'm not really fit with cardiology, so I can't think of realistic examples). There is a lot of thought that has to go into this. And more standards...because this is a piece of hardware, you'll need to look into IEC 60601-1 and its more detailed offspring. I am sure however that someone has told your boss about all this or that he has asked someone about it. As to your last question: The IEC 62304 is "merely" a software standard and to understand it fully you'll need to invest some time and/or take some classes such as this https://www.bsigroup.com/en-GB/medical-devices/training/Introduction-to-Medical-Device-Software-Training/ the cost of this particular course should give you an indication as to where the trip is going. Calculate roughly the same for a 13485 course - per person attending, mind you. Then you'll definitely need to know and use the IEC 14971, there are courses too i.e. https://www.bsigroup.com/en-GB/medical-devices/training/iso-14971-2019-risk-management-for-medical-devices/ Then your company should be fit to give it a go. By that time you have to find and auditor. That is a notified body (directly or indirectly accredited and certified by the government) who will check all documentation as I stated earlier. And they don't do this out of the goodness of their heart. Calculate at least 10k€ for this, once a year for the rest of the companies life. All in all prepare to invest around 50 k€ in "compliance" alone. Another really good summation can be found here: https://www.cognidox.com/medical-device-development-guide

I should correct my statement as to what is needed to market: Most important is the declaration of conformity, and how this was obtained, the "conformity assessment route". There are many ways to reach conformity, but some are actually the same... I have a german link to explain further...not english, sorry: https://www.johner-institut.de/blog/tag/konformitatsbewertung/

Is this still the case when you declare the type as well? var combinedPath: string := TPath.Combine(ParamStr(0),'..\..\..\'); var curPath:string :=TPath.GetFullPath(combinedPath);

That sounds dismal. What struck me though is this: How does this make any form of version management possible? If every developer has their own style they might be tempted to reformat code as they work on it, causing a multitude of changes and in essence a merging nightmare.

@Rollo62 HA! Nice! Johner Institute is my helper to get through this tedious process I can really recommend them.

There are plenty of applications created with Delphi, that are conform with 62304. My own application for example. 62304 does not demand the use of certain languages, it does however require extensive documentation. Documentation you should have anyway... Have you read anything concerning this standard? Wikipedia grants us a small glance at the implications: https://en.wikipedia.org/wiki/IEC_62304 I would suggest to consult more in depth literature and courses however. The subject is not trivial, especially the risk based decision model, that should be used in almost all aspects of the software life cycle. Auditors or accreditors as you call them, will not read your source code, as that is proprietary to you and your company. They will however read the entire technical documentation. Most important is the market you want to sell your product, if it is Europe, you will need more that IEC 62304. You will need to adhere to the medical device regulation (MDR 2017/745) and that means you'll need to establish a company wide quality management system such as the ISO 13485. And you'll need certification before selling anything. All in all this will swallow up a ton of money before you can even start thinking about generating any revenue.

Well, there's your answer. And also why SO has banned AI generated answers. So...actually no need to start a new thread. Just chime in one of the other threads:

There has been a fix for the Win32 compiler. Perhaps a test run and a sign that there is something happening in Embarcaderoland: https://quality.embarcadero.com/browse/RSP-39812

It was called Eliza back then. ChatGPT is just Eliza on Steroids.

Almost every "call" is potentially dangerous. Asking for a language or a dialect of an existing language without potentially dangerous calls will leave you with nothing, hence the lack of answers from the people you contacted. It is up to you to find out what weaknesses a language has and how to either overcome them or, if to cumbersome, avoid the language altogether. Then you also have to take into account the security issues the system running your software may have. Windows has quite the "rap sheet", when it comes to vulnerabilities. But still it is a solid OS to run your software on, if you are aware of these issues. You may choose to run in a browser...that in itself may expose you to new risks you'll have to learn about, risks that may even be specific to the OS running the browser, so you'll end up checking out combinations of browsers and OSes even over different versions, a ton of permutations to evaluate. And so far you haven't even looked at hardware. What about the USB ports on a standard PC? How can you verify that they are not misused? As you see cyber security is very expensive, thinking about what might go wrong is just the first step of many. Real security however is just an illusion, just like the idea of error free software. What you need to have is risk assessment together with a catalog of countermeasures and assess how useful or indispensable your software really may be. If the benefit-risk-ratio is acceptable, go ahead build your software, if not... I seem to have drifted of, sorry.

ChatGPT is way to verbose with its answers and takes forever to finally get to the point. I don't consider it fascinating, and I don't consider it to be an AI. It has had it's moments and those have been enough for one investor or another to inject money into the project or to actually assume they might be able to put it to use (Bing - imagine the loooong answers for a simple search). In short ChatGPT is Eliza without the need to program responses but have responses stored in a DB filled by training.

You want to compare two binary files, if I understand correctly. Here is a program that does that: https://www.cjmweb.net/vbindiff/

No, it means you can install Skia4Delphi and use it in your project, and after following the steps pointed out to you, you can use "right to left" as originally expected.

Also keep in mind, if this software is supposed to be commercial you will have to look into encrypting the communication. TLS will have to be minimum.

I would have put that check into an SMTP server. And...surprisingly the good ones do that.

Given the complexity and the tendency of developers to always suggest some totally different approach , here is my completely different suggestion. You seem to have the need to validate an e-mail address before storing it. How about sending a test mail before doing that. That way you get to birds with one stone: Verify the address, and get the permission to use it... a must have in Europe.

Oh, right! I just had the Master in mind. And that I am not...

I don't think I could pass the exam But some of our MVPs such as @Uwe Raabe have, perhaps he might share some insights.

Well take a step back then. Do you know what you are doing? You are mixing two things here, maybe at first try this with just the important one and save the syntactic sugar of inline variables (which may still be buggy) for later: procedure TGISEngine.AddFilenames(const AFilenames: TGISFilesnamesSHP); var F: string; // I'm just guessing here, and maybe that is the compilers issue as well begin if (Length(AFilenames) > 0 ) then for F in AFilenames do if not FFilenames.Contains(F) then FFilenames.Add(F); end; Later on, you may read what the Docwiki has to say about the limited abilities the compiler has regarding type inference and discover their examples for inlines in for...in loops all have a type declaration.

Just my two cents as a person who has been developing commercial software with Delphi for over 20 years now (where has all the time gone? sigh). Whenever there have been issues with the software, one thing turned out to be true: The DB was almost always the problem. That, or the way DB data was being handled. Rethinking table design and handling of DB-aware and not-DB-aware components have always done the trick. But feel free to produce a minimal reproducible example for the folks at Embarcadero, if you are 100% sure that Delphi is at fault.

That is a good thing. Anything built into Delphi slowly decays due to lack of maintenance. Until one day it produces only errors and management has to decide wether to trash it or build something around it to try and fix it. Most prominent recent example: ErrorInsight fixed through LSP. Or the Parnassus tools...taking longer and longer to appear in GetIt with each new Delphi version.

For an deeper understanding read here: https://www.exploringbinary.com/why-0-point-1-does-not-exist-in-floating-point/ And this is your solution: https://docwiki.embarcadero.com/Libraries/Sydney/en/System.Math.IsZero if you want to check for zero values.

My hammer beats every other tool every time.

Everybody cool down please, and don't get personal. Thank you.

Well, which Windows version is this? Windows 7 is not supported anymore, AFAIK.