Skip to content

Conversation

@Vizit0r
Copy link
Contributor

@Vizit0r Vizit0r commented Aug 19, 2019

  1. fix of OPENARRAYOFU16 and OPENARRAYOFS16 declarations
  2. DynArray "out of range" errors extended, now included info about curr index and array length
  3. uPSUtils - takilng ansi string length from 0 index - changed to correct Length() calling.
  4. added names forming for dynarrays when compiling.

2) DynArray "out of range" errors extended, now included info about curr index and array length
3) uPSUtils - takilng ansi string length from 0 index - changed to correct Length() calling.
4) added names forming for dynarrays when compiling.
@carlokok carlokok merged commit 51a015c into remobjects:master Aug 20, 2019
{$IFDEF CPUX64}
IPointer = IntPtr;
{$IFDEF VER140UP}
IPointer = NativeInt;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Vizit0r What's the reason for this change? It seems unrelated to the list of changes listed in the pull commit. This change causes a whole load of 'W1024 Combining signed and unsigned types' warnings.
Fyi @carlokok

btString:
tbtstring(dest^) := PSGetAnsiString(Src, srctype);
btChar: tbtchar(dest^) := tbtchar(PSGetUInt(Src, srctype));
btChar: tbtchar(dest^) := PSGetAnsiChar(Src, srctype);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Vizit0r This change is not explained by the commit comment? Why was it made?

if srctype.BaseType = btClass then
TObject(Dest^) := TObject(Src^)
else
if srctype.BaseType = btVariant then
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Vizit0r This change is not explained by the commit comment? Why was it made?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

canot say exactly, but i remember, that long time ago i have some bug with classes, thats why this line has been added. But that was really LONG time ago, so no details.
Are there any problems due to this fix observed?

end else v := nil;
try
Result := Caller.InnerfuseCall(FSelf, p.Ext1, {$IFDEF FPC}TPSCallingConvention(Integer(cc) or 64){$ELSE}cc{$ENDIF}, MyList, v);
Result := Caller.InnerfuseCall(FSelf, p.Ext1, TPSCallingConvention(Integer(cc) or 64), MyList, v);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Vizit0r This change is not explained by the commit comment? Why was it made?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change is need to explain for InnerfuseCall x86 that constructor called.
For InvokeCall.inc this has no matter.

And yes, it should be covered by conditional define USEINVOKECALL

martijnlaan added a commit that referenced this pull request Dec 20, 2025
1) fix of OPENARRAYOFU16 and OPENARRAYOFS16 declarations (#205)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants