tag:blogger.com,1999:blog-1077468864044303325.post3017868246512925351..comments2024-03-20T18:47:57.268+02:00Comments on Behind the connection: Delphi XE4 and AnsiStringFPiettehttp://www.blogger.com/profile/08260455911271500004noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1077468864044303325.post-32886099540531657632013-06-10T04:03:21.040+02:002013-06-10T04:03:21.040+02:00Thanks for such an elegant solution!
Thanks for such an elegant solution!<br />Cesar Vegahttps://www.blogger.com/profile/02568695850350231640noreply@blogger.comtag:blogger.com,1999:blog-1077468864044303325.post-35801682587181824132013-04-30T14:42:33.305+02:002013-04-30T14:42:33.305+02:00I experienced the same problem in GExperts and sol...I experienced the same problem in GExperts and solved it by by adding my own inlined function StrLen at the top of the unit like this:<br /><br />{$ifdef DelphiXE4}<br />function StrLen(a: PChar): integer; inline;<br />begin<br /> Result := System.AnsiStrings.StrLen(a);<br />end;<br />{$endif}<br /><br />This saves all those untidy ifdefs scattered around the code.dummzeuchhttps://www.blogger.com/profile/10964052286248095908noreply@blogger.com