DelphiUdIT

http://docwiki.embarcadero.com/RADStudio/Athens/en/64-bit_Windows_Data_Types_Compared_to_32-bit_Windows_Data_Types

I agree with you on what you say, the pointer problem is indeed a problem, and obviously needs to be solved. But the incompatibility with 64-level DLLs and ASLR is well known: at one of the webinars, following a direct question of mine on this very topic (we were talking about DLLs with C++ and Delphi), it was confirmed that full compatibility between 64-level DLLs and ASLR could not be guaranteed when developed with C++ (Embarcadero). We talked about this a few months ago. Whether the problem is with the C++ libraries (perhaps some still 32-bit pointers?) or something else has never been clarified. However, I correctly use 64-bit DLLs developed in C++ Embarcadero with ASLR and ASLR HE without any problems.

I think the problem is the project options: in the new 11.3 (like 12) environment the additional setting about ASLR are ON, try to deselect them.

@pcoder, @Stefan Glienke I think he wants to try a general function, also for others rounding modes (he inserts other masks to the function). But you are right, there are also other native CPU instructions that do that specif works (like that you exposed).

But use the "grep" tool on command line to check where the unit are related, in all files (in all disk if necessary 😉) ?

But is not forbidden:

If you must use NEW (so create a new variable), why don't declare it like a normal variable or a typed pointer? If you refer a record variable you don't need to allocate memory. If you need to reference a pointer, this normally means that it's already assigned and you can cast without NEW or DISPOSE. Another suggestion: in Delphi you don't need to "defererence" a typed pointer, the compiler do it for you: var LPointer : Pointer; begin New(PMyRec(LPointer)); PMyRec(LPointer).Int := 200; PMyRec(LPointer).Str := 'Blah'; Dispose(PMyRec(LPointer)); end; var LPointer : PMyRec; begin New(LPointer); LPointer.Int := 200; LPointer.Str := 'Blah'; Dispose(LPointer); end;

I don't understand what is bad here. "FloattoJson" means transform a float value in Json reppesentation ... and this means that should be ".x" in the case that there are not "." or "E" symbol. This is true and not questionable, but the real meaning to know if that Json format is a "standard" float or a currency is in this phrase: So, I can write this values: (1) <- May be a integer, but you can read it like "base 10", binary, hex, octal .... (1E0) <- May be a integer, but also a float (and I saw the scientific notation generally is taken like a float) and yes it's "base 10" (1.0) <- It's a float "base 10" or currency ? (1.00) <- It's float "base 10" or currency ? But all this representations are subjective to Json ....

Most often this happens if you use third-party components. Try uninstalling add-ons (such as those installed by GETIT) one at a time to find which one might be generating the AV (assuming it depends on the added components).

May the be graph attached in that post ? https://en.delphipraxis.net/topic/10229-unit-dependency-viwer/?do=findComment&comment=81286

It wasn't for you my reply. You are from TeamB and an MVP Embarcadero, I have nothing to explain, signaling some issue may be but sure not explain to you. The post was for @Adam and for other readers.

UseLatestCommonDialogs: Boolean = True; MsgDlgIcons: array[TMsgDlgType] of TMsgDlgIcon = (TMsgDlgIcon.mdiWarning, TMsgDlgIcon.mdiError, TMsgDlgIcon.mdiNone, TMsgDlgIcon.mdiNone, TMsgDlgIcon.mdiNone); This is how they delete the standard dialogs (MessageBox) icons, except for Warning and Error.

To be more "simple: 1) You can refer in the "requires" section simple with IndyProtocols for example, but the library (bpl) used will be with "290" ... or the new extension for Delphi 11 or Delphi 13 ....; 2) So in every component will you refer in the future you'll refer ALWAYS to with "IndyProtocols" and depending of IDE version will linked to the correct BPL version (280, 290, 300, ....); This require the changes the name of the DPK/DPROJ files, the changes of the "requires" sections and the use of $LIBSUFFIX = AUTO (in the DPK and in the DPROJ files). In the past that was done using LIBSUFFIX (for example) with "290" instead of AUTO. The libraries in RAD STUDIO are related without suffix "290" but the BPL still have those suffix (for example you refer to RTL in the DPK files not RTL290). "NEW" WAY "OLD" WAY Bye

I would said that there are some tickets "open" and others "closed" about that.

There are a lot of github repo to OpenCV for Delphi, this is another one: https://github.com/gidesa/ocvWrapper46

This is right if you want maintain the full compatibility with Embarcadero and all third parts packages. But this is not all, you must set also the $LIBSUFFIX to "AUTO", because the BPL packages should be named with "290" version. Indy packages in the repo are not set for this, there are some "ticket" open (and "closed") about this. I wrote some posts about substitute the original Indy and restore the compatibility with Embarcadero environment, but after last changes in Indy repository I will rewrite again a full post with all steps in simply mode including openssl indy repo and ssl-oauth indy repo, possibly via script.

I compiled the new Indy package (https://github.com/IndySockets/Indy/tree/sasl-oauth) in Android platform too with success. Three issues found: 1) In the IDHL7.PAS, after the implementation section two uses files do not exists. Comment out there will be no apparent issue. In the Embarcadero release IDHL7.PAS is not present. 2) In the IdCompilerDefines.inc there is a $DEFINE (HAS_getifaddrs): I had undefined that since one records that will be used if that define is in use in Android platform is never delclared. 3) One settings on Embarcadero Rad Studio path is wrong, should be Android not OSX - this is for both Android 32 and Android 64: After those modifies, I was able to compile the Indy for Android. I try also an old Android project with IdSMTP protocol (with SSL) without any issue.

I used the last update branch (SASL-OAuth) yesterday night.

What components were dropped ? I replaced totally Indy without any issue, restoring also the IDE functionalities. I think that DevEx (if it recompile the units) should no have issues. Edit: I tested quickly the old project that use the IdSmtp, IdTCP, IdFTP, IdHttp all with SSL and were no change on compilation. I don't use IdPop3.

I think @Remy Lebeau is working on repository branch of SASL-OAuth. UPDATE: I updated this repository in Rad Studio and TLS1_3 is working, an also the OAUTH2 is available on the component palette. Waiting for @Remy Lebeau news.

Why you don't use only the modified files along with yours projects (in a common repository for example) instead to porting all Indy environment ? I use Indy from a long time and I never saw a big changes. I used in the past ( very past ) to modify some IdAuto* protocols 'cause incompatibility with private Servers (MD5 bugged ... and stay bugged on their side). Bye

The source of those files (idoc and idispids) are under "source/internet" (from Rad Studio base dir). The date of the files of course are like the others, but internally they are generated on 1998 from typelib. I think they are related to Internet Explorer. I don't know why I have them and you don't. I have all the platforms installed (Rad Studio Enterprise edition). Play* are from android environment. If make a "del Id*" from batch file, only the "idoc and idispids" are interesting, from explorer all the others are presented. You can copy those files (idoc and idispids) to a backup place and restore after delete. Others way is to delete only a list of know files. Both methods, however, require monitoring of patches and environment updates.

@jesu You can open a ticket from support if you have a subscription.

... from previous post, instructions to restore all Indy functionality inside IDE. Go to Rad Studio installation directory (normally "C:\Program Files (x86)\Embarcadero\Studio\23.0"), in the "source" directory. Inside the "source" should be present 3 Indy folder: "indy", "Indy10" and "indyimpl". Indy10 is the real source of Indy like that in the GitHub. Instead, "indy" and "indyimpl" are the folders that contains the IDE functions implementations of Embarcadero. The path is protected, so copy these to folder (with the content of course) somewhere ... I copied them where are the new Indy source (look at https://en.delphipraxis.net/topic/6844-tls-v13/?do=findComment&comment=88750), changing the name of "indy" in "indyextra". EDIT: Forgot to insert the new path in the browsing property. You must insert the path of the new folders inside the browsing property of TOOLS/OPTIONS/LANGUAGE/DELPHI/LIBRARY of the IDE. If there are the originals, you must overwrite them. Of course that in the image are mine, you must set yours. Now you have to build some packages and install some of them. In the new "indyextra\implementation" build the packages present in this sequence: 1) IndyIPCommon.dpk; 2) IndyIPClient.dpk; 3) IndyIPServer.dpk ATTENTION: depends how you build the new Indy packages, you should change the name of the 3 requires packet (IndyCore, IndyProtocols, IndySystem) referred in the DPK source files. This is for every packages that you compile with Indy. After that go to "indyimpl" folder and BUILD and INSTALL the "dclIPIndyImpl.dpk". Now you have restored the original functionality inside the IDE ("FIREUI Live Preview" and " Embarcadero RAD Server Edge Components"), and you can install also the new packages that require those functions inside the IDE. BUT ONE MORE STEP NEED TO complete the work: you must change the Windows registry, because when you install the new Indy from github repo you have disabled permanently two Embarcadero packages. Pay attention to what you are doing with Windows registry. Open the registry with command prompt "regedit" and go to this section: "HKEY_CURRENT_USER\Software\Embarcadero\BDS\23.0\Disabled IDE Packages" Delete the key "$(BDS)\Bin\LivePreview290.bpl" Now go to next section "HKEY_CURRENT_USER\Software\Embarcadero\BDS\23.0\Disabled Packages" and delete the key "$(BDSBIN)\dclemsedge290.bpl" Now you can restart your IDE and you'll have the full functionality. Indy works like always, and if you want to use the "new" TLS1_3 you must do some coding (also mixed designtime / runtime). But this is another chapter ... Happy work.

The "Jedi Common Files" aka jedi.inc / kylix,inc are in the repository: https://github.com/project-jedi/jedi You must extract this two files in the 'jcl\source\include\jedi' directory.