<HTML><HEAD>
<STYLE id=eMClientCss>BLOCKQUOTE.cite {
PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccccc 1px solid; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px
}
BLOCKQUOTE.cite2 {
PADDING-TOP: 0px; PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccccc 1px solid; MARGIN-TOP: 3px; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px
}
.plain PRE {
FONT-SIZE: 100%; FONT-FAMILY: monospace; FONT-WEIGHT: normal; FONT-STYLE: normal
}
.plain TT {
FONT-SIZE: 100%; FONT-FAMILY: monospace; FONT-WEIGHT: normal; FONT-STYLE: normal
}
A IMG {
BORDER-TOP: 0px; BORDER-RIGHT: 0px; BORDER-BOTTOM: 0px; BORDER-LEFT: 0px
}
#x08cbef7a594047c290f2a29cf59a1a5a {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
#x0a1e5b0435564365913781b92e976507 {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
#x2d29ccc5fc9b457885b0b979f991396b {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
.plain PRE {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
.plain TT {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
BODY {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
</STYLE>
<STYLE>#x0a1e5b0435564365913781b92e976507 BLOCKQUOTE.cite2
{PADDING-TOP: 0px; PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccccc 1px solid; MARGIN-TOP: 3px; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px}
#x0a1e5b0435564365913781b92e976507 .plain PRE, #x0a1e5b0435564365913781b92e976507 .plain TT
{FONT-SIZE: 100%; FONT-FAMILY: monospace; FONT-WEIGHT: normal; FONT-STYLE: normal}
#x0a1e5b0435564365913781b92e976507 A IMG
{BORDER-TOP: 0px; BORDER-RIGHT: 0px; BORDER-BOTTOM: 0px; BORDER-LEFT: 0px}
#x0a1e5b0435564365913781b92e976507 #x08cbef7a594047c290f2a29cf59a1a5a, #x0a1e5b0435564365913781b92e976507 .plain PRE, #x0a1e5b0435564365913781b92e976507 .plain TT, #x0a1e5b0435564365913781b92e976507
{FONT-SIZE: 12pt; FONT-FAMILY: Tahoma}
</STYLE>
</HEAD>
<BODY scroll=auto bgColor=#ffffff class>
<DIV>Well. About the non <SPAN id=x2d29ccc5fc9b457885b0b979f991396b style="BACKGROUND-COLOR: #ffffff">compatible. I can only detect these:</SPAN></DIV>
<DIV><SPAN style="BACKGROUND-COLOR: #ffffff"></SPAN> </DIV>
<DIV><SPAN style="BACKGROUND-COLOR: #ffffff">1)</SPAN></DIV>
<DIV>RTTICount: Word; //$FFFF if there is no further info, or the value of Count</DIV>
<DIV>I did not see it set to $FFFF in case of missing RTTI. As Delphi reportedly does.</DIV>
<DIV>But perhaps this has already been done somewhere else.</DIV>
<DIV> </DIV>
<DIV>But, in my opinion, this is not of much importance</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>2)</DIV>
<DIV>Properties are in front of methods.</DIV>
<DIV>This is different from Delphi.</DIV>
<DIV>But I know that this cannot be changed.</DIV>
<DIV>That would break a whole lot of code !</DIV>
<DIV>And again, if you are aware of this: no problems at all.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>So, for me, this is all ok now !!</DIV>
<DIV> </DIV>
<DIV>And I am willing to test on simple ARM (Pi[2], BBB).</DIV>
<DIV>If you provide me with code !</DIV>
<DIV> </DIV>
<DIV>Thanks again, Alfred.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------ Origineel bericht ------</DIV>
<DIV>Van: "Steve Hildebrandt" <<A href="mailto:Steve.Kassel@web.de">Steve.Kassel@web.de</A>></DIV>
<DIV>Aan: <A href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</A></DIV>
<DIV>Verzonden: 25-2-2015 19:16:17</DIV>
<DIV>Onderwerp: Re: [fpc-devel] RTTI interface & variant late binding issue (mORMot)</DIV>
<DIV> </DIV>
<DIV id=x0a1e5b0435564365913781b92e976507 style="COLOR: #000000">
<BLOCKQUOTE class=cite2 cite=54EE1171.8060901@web.de type="cite"><BR>
<DIV class=moz-cite-prefix>Am 25.02.2015 um 18:47 schrieb Alfred:<BR></DIV>
<BLOCKQUOTE class=cite cite=mid:eme7d9897e-2830-4c71-a2c8-15dd05566980@alfsacer type="cite">
<STYLE></STYLE>
<DIV>Hello Steve, all,</DIV>
<DIV> </DIV>
<DIV>I would like to report 100% success with the latest RTTI patches !!!!</DIV>
<DIV> </DIV></BLOCKQUOTE>Nice to hear.<BR>If anything is not compatible with the information delphi provides please report back to me.<BR>
<BLOCKQUOTE class=cite cite=mid:eme7d9897e-2830-4c71-a2c8-15dd05566980@alfsacer type="cite">
<DIV><SPAN id=x8502058b63334714918fdda8ce0077e0></SPAN></DIV>
<DIV>One (first) request:</DIV>
<DIV>Would it be ok to add pfConstRef to the TParamFlag in typinfo.pp ?</DIV>
<DIV> </DIV></BLOCKQUOTE>The RTTI should already be generated the enum value was simply missing. <BR>See attached Patch.<BR>
<BLOCKQUOTE class=cite cite=mid:eme7d9897e-2830-4c71-a2c8-15dd05566980@alfsacer type="cite">
<DIV><SPAN id=x08cbef7a594047c290f2a29cf59a1a5a>
<DIV>One (second) request:</DIV>
<DIV>The same RTTI on ARM would also be very welcome.</DIV>
<DIV>As stated before, my interest is running mORMot on ARM (e.g. Raspberry Pi[2]).</DIV>
<DIV> </DIV></SPAN></DIV></BLOCKQUOTE>Since I'm unable to test it myself right now, I could only try to write this blind and let somebody else do the testing.<BR>It would also help to know what calling conventions are supported and how they work if they are not compareable to the i386/x64 ones. <BR>(Link to a good documentation or a short write up)<BR>The other way this could work is, if somebody with an ARM system takes over and I explain where compiler changes need to be made.<BR><BR>mfg Steve<BR></BLOCKQUOTE></DIV></BODY></HTML>