-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug fixes & changes in InvokeCall.inc #225
base: master
Are you sure you want to change the base?
Conversation
2) added Interface to result types list 3) Changed flag IsStatic for x64 for "String" type, so Strings will be passed and returned to\from Delphi methods correctly in x64. 4) added notice about using types-synonyms
@Vizit0r Can you check the conflict? I'll try to merge it next week. |
Some ideas for "openarray,record,set,fpc,xe3" |
@carlokok i remember 1 thing, whick cause changes all over the PS files.
but in this case ALL "LongInt" in ALL PS files must be changed to LongInt4b. Looks not so good. All other changes still checking. Also, will look @pult InvokeCall.inc |
This comment has been minimized.
This comment has been minimized.
2) types fixes and other common changes for POSIX
Joined. |
@pult i cant write you, thats not a chat, but channel. |
…Ptr in x64, should be fully rewritten @MyAllMethodsHandler & MyAllMethodsHandler2) Tests for Android will be done in 1-2 days, after finish will update + attach tests.
1) added support of all 64bits platform on Delphi (not only intel x64). Also Delphi 10.4 added. 2) InvokeCall.inc fully tested (about tests later on) in Delphi on Win x86 + x64, MacOs x64, Linux x64, Android 32b + 64. IOS not tested (i have no iphone etc), and simulator is very slow). All PS types supported, in params and result. 3) Included folder "Invoke Tests", which contains tests for Delphi VCL (Win) + Delphi FMX(all paltforms) + FPC. 4) FPC failed almost all tests. I have not enough FPC skills and power to find a right way with ugly debugger in FPC Invocation, who is strong enough - finish it pls. 5) about calling scripts methods from Delphi for non-Windows systems - its still not completed, i have no time at the moment for this - but i know the way, and will do this later on. It's not the most important and popular thing, really.
@carlokok i have finished all. |
okey guys, revert changes, as you want. Tests - its also nothing, code is undocumented. Normally, who wants to see the explanation - read a commits comments. Have no idea, why you dont want to go this way. Good bye, and happy new year. |
Just giving my opinion, it's up to Carlo what happens. It's a fact though that your commits contain changes which don't match the commit descriptions like 8ef297c which has an additional debugger related change and 3b2cabe which has an additional change that looks like a memory leak fix. These are just 2 examples. These changes might be good and intentional but that can't be seen from your descriptions. I've pointed this out in earlier commits by you which also contained unexplained changes. One of the commits has a change to uPSRuntime so large that Github can't even display it. This isn't how you're supposed to make pull requests. Here's a good explainer if you're interested: https://www.jamescroft.co.uk/a-guide-to-making-a-good-pull-request/ The biggest problem of a pull request like this one that it's way too big and doesn't focus on a specific area, making it impossible to properly review. |
i've not comment EVERY small change, if its not critical or important. F.e. in 8ef297c adding one more condition for checking in "LineInfo" - thats for preventing error, which my user have, very rare error, but its exists. Thats much more explanation, what its done for, than real code. Others same. I have a lot of changes, which i dont include in my commits, because i'm not sure it can be useful for someone else. About the rules of commiting - i've never read it, works only with repos alone or in small commands, there were no any problems with my commitment style. Anyway, @carlokok should decide. If question only in commits styling, i can spent a lot of time and divide them again, but size of some of them cant be decreased. |
Resolves #241 |
Thats jut to to access field in same manner, as all over the PS code.
i dont make an aim to change it anywhere, what i see - i change to common manner. |
… - decided to use RTTI types prior to "TypeByKindSize" (with caching RTTI types for corresponding script types names) 2) in uPSRuntime.pas added "Generics.Collections," to uses + fixed invokecall define in FPC 3) fixed bug in uPSPreProcessor.pas for correct parsing of non-Win linebreaks (remobjects#10 instead of remobjects#13#10 in Win). 4) Added POSIX define to uPSPreProcessor.pas
Nothing so, just some small fixes & changes. P.S. InvokeCall works like a charm.
Source/uPSUtils.pas
Outdated
{$IFDEF DELPHI2009UP} | ||
IPointer = NativeUInt; | ||
{$IFDEF VER140UP} | ||
IPointer = NativeInt; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you change this definition? #233
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed, have no idea, why VER140 was written there.
P.S. Native(U)Int coming from XE2, not from 2009.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, look into #233 - you should change all definition block for IPointer
.
Versions prior XE2 do not have support Win64 at all, so you don't need to check for CPU64 etc.
…t version only, so mess it. Thanks @zedxxx for notice.
Issue numbers:
#219
#218
#217