It’s Delphi, but I’ve not seen practical implementations in C# either.
(the updated version thanks to Anders Melander).
–jeroen
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Since I wanted to follow his “blog” (which is sort of a collection of WordPress pages, mainly about the programming OTA: the Open Tools API interface to Delphi and C++ Builder), I was looking for the RSS feed.
… Only a perfect licensing system would actually do you any good, and there’s no such thing. And in the age of the Internet, if your system isn’t perfect, all it takes is for one person anywhere in the world to produce a crack and upload it somewhere,
…
If you want people to pay for your software instead of just downloading it, the one and only way to do so is to make your software good enough that people are willing to pay money for it….
It takes a MAP file from your Delphi compiled executable that has debug information in text format which means you need to set your project linker options to generate detailed MAP files.
I’ve learned to not update Xcode, OSX or iOS until absolutely necessary, and even then I usually stick with an older version of Xcode that is known to be compatible with Delphi. It takes a while for Embaradero/Idera to fix issues every time Apple makes some breaking change. I recommend rolling back to an earlier version if you can.
Vendors should post these, but alas Embarcadero is not the only one failing here, so here are build/version numbers of the various Delphi Berlin releases until now:
When you ship OpenSSL DLLs, you should provide an update mechanism outside of your regular product cycle that updates these shortly after vulnerabilities are fixed.
Few if any products do that. So I made an overview from products and OpenSSL DLL versions I had installed on various systems.
I’m a developer, so the list is biased towards tools I use often.
In recent Delphi version, FastReport version 5 ships. But for parts of FastReport, it’s a trial. This includes the FastScript part. The trial is very close to the real FastReport 5 thing. So real that when you compile you don’t see a difference, not even when trial and official things are mixed.
The only difference is that the trial will have a ShowMessage result like this:
ShowMessage(‘Unregistered version of FastScript’);
[Window Title]
Fastscriptexecute
[Content]
Unregistered version of FastScript.
[OK]
This occurred when I tried to move a the build process to a build server; a very tiny program will show this:
program FastScriptExecute;
uses
Vcl.Forms,
fs_iinterpreter;
{$R *.res}
var
fs: TfsScript;
begin
fs := TfsScript.Create(nil);
try
fs.Execute();
finally
fs.Free();
end;
end.
The build server had Delphi installed but not FastReports 5. I put all the sources in version control and fiddled with the project search paths until it built on the server.
Wrong!
Since the trial is so close to the real version, it will compile even if you don’t include all directories. In fact some permutations of the FastReports source and Delphi XE8 FastReports trial DUCs build perfectly fine.
The Wiert Corner - irregular stream of stuff 