ROServiceImporter on Swift for XCODE

Dear staff,
I am testing the newest version of Remobject with swift for Xcode 8.2.1
when I use the ROServiceImporter to generate the swift files and compile in Xcode there are many errors,
but with Object-c(Xcode) it works well.
how should I do on this ?
below is the image for errors

Just to be sure i have the full picture, can you send me the RODL file you used? thanx! That said, it looks like some adjustments are needed to the codegen for recent Swift 3 changes; i’ll get those looked at ASAP, for the next beta.

thanx,
marc

Thanks, logged as bugs://77289

I was created the sever in Delphi ro sdk template
Add nothing on it .
I think it was the bug of code generator.

Thanks!
Jason

Dear Marc,
when do you think I should check if any update on beta to download?

I believe i have the core issues in codegen fixed, please try the attached version. That said, can you please send me the exact project you are using, inlcuding the RODL? thanx.

rodl2code.zip (2.6 MB)

Fixed a couple more. If there’s anything left, i really do need the project. thanx!

rodl2code v2.zip (2.6 MB)

Hi Marc
Here is the projecttestPrj.rar (107.5 KB)

but still 588 errors with the new one.

The Xcode project :wink:

This is with the first version i sent, though,not the second one, right?

yes
it was created with the newest one.
here is the Xcode project:TTT01.zip (325.3 KB)

Curious, because in the new one i fixed enums not getting the open keyword…

In any case, i can now reproduce a number of additional issues that need fixing, i’ll try and address them later today and send you new CG. Man, Apple broke a lot of stuff once again, with the latest Swift…

i apologize for the inconvenience.

It’s OK,

I am not rush,

Thanks for your help.

Thanks!
Jason

发件人: marc hoffman talk@remobjects.com
答复: RemObjects Talk cc5fe9202532420f8703c6aacc940e70@talk.remobjects.com
日期: 2017年2月23日 星期四 下午10:55
至: jason_li jasonli@go2cap.com
主题: Re: [RemObjects Talk] [Remoting SDK] ROServiceImporter on Swift for XCODE

mh marc hoffman chief architect
February 23
In any case, i can now reproduce a number of additional issues that need fixing, i’ll try and address them later today and send you new CG. Man, Apple broke a lot of stuff once again, with the latest Swift…

i apologize for the inconvenience.

Visit Topic or reply to this email to respond.

In Reply To
mh marc hoffman chief architect
February 23
Curious, because in the new one i fixed enums not getting the open keyword…

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

that’s good, as this is gonna take forever :(. i keep finding new depths of stuff Swift 3 broke, beyond just plain method mangling (which is causing the majority of the first round of issues i now fixed). Hopefully i’ll get it all sorted tomorrow, but i cannot promise.

—marc.

Just to keep you in the loop. I managed to fix all issues on friday, but it involved some changes to the library (for swift_name annotations) as well as the codegen itself, so jut seeing you a new codegen won’t do the trick, the next beta build (probably wednesday) will have all the fixes. Do you currently have beta access?

yours,
marc

I can download the beta, it’s not rush , just let me know when it fixed .

Thanks for you kindness help .

Have a good day.

Thanks!
Jason

发件人: marc hoffman talk@remobjects.com
答复: RemObjects Talk af357c42291fb2181f7af197dda70b21@talk.remobjects.com
日期: 2017年2月27日 星期一 下午8:13
至: jason_li jasonli@go2cap.com
主题: Re: [RemObjects Talk] [Remoting SDK] ROServiceImporter on Swift for XCODE

mh marc hoffman chief architect
February 27
Just to keep you in the loop. I managed to fix all issues on friday, but it involved some changes to the library (for swift_name annotations) as well as the codegen itself, so jut seeing you a new codegen won’t do the trick, the next beta build (probably wednesday) will have all the fixes. Do you currently have beta access?

yours,
marc

Visit Topic or reply to this email to respond.

In Reply To
mh marc hoffman chief architect
February 23
that’s good, as this is gonna take forever :(. i keep finding new depths of stuff Swift 3 broke, beyond just plain method mangling (which is causing the majority of the first round of issues i now fixed). Hopefully i’ll get it all sorted tomorrow, but i cannot promise. —marc.

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.