Another interesting potential stumbling block for XE4.

Another interesting potential stumbling block for XE4.

“To keep up with the notion of eliminating pointers, the new compiler requires an explicit style of marshalling data to/from external APIs and libraries.

This can be accomplished by using the high-level marshalling API TMarshaller: 

or the low-level TMarshal:

I wonder if this is limited to the iOS compiler, or if it applies to x86/x64 too?

11 thoughts on “Another interesting potential stumbling block for XE4.

  1. “meeeh” — thinking that objective-c is way better, imagine when you hit a brick wall, whom do you turn to on SO:

    Delphi | iOS(a few thousands — maybe)


    XCode | Objective-C(>= million)


  2. Dorin Duminica The number of questions is only a problem if questions aren’t getting answered, which doesn’t seem to be the case.  And as of right now, the tag “delphi” has 20,226 — more that “a few thousand”.

  3. Uwe Raabe like with everything, you can look at it from different angles, it’s not really a matter of language IMHO, ios is a different platform, I guess we’ll have to wait and see, but I’m afraid that the market will be filled with shiny components for the ios, most of which useless and the compiler will fail to deliver the expectation.

    Don’t get me wrong, I would love Delphi to be a choice for ios/android/etc. much better than having to learn yet another language and another way of doing this, however, I’m not going to hold my breath.

Leave a Reply