Does EA support code engineering for Objective-C?

[OwenInCanada]

Hello all,

Does EA support code engineering for Objective-C?

My colleague installed the 11.1 trial edition and Objective-C is not listed in the dropdown menu at
EA>tools>Source Code Engineering>import source directory>Source Type .

Doxygen will give us a simple understanding of which Objective-C files refer to other files, but I still haven't found a tool that is based on call graphs.

(Admittedly there is a Mac/PC culture clash between Objective-C and EA. But why should that stop us, its just a directory tree with text files, right?)

Thanks,
Owen

[qwerty]

Nope. The windozers don't know that. Of course they also don't know about Swift.

q.

P.S. I started writing a Objective-C to XMI compiler but have stopped that a while ago. Maybe if I got time I'll continue with Swift. Or I'll try the BNF syntax description you can feed into EA.

[Eve]

If you're after the call graphs, then I believe the GDB debugger can do that for Objective-C even though we don't reverse engineer the structure.

From memory Objective-C had some weird things that made it a little hard to parse (or map to UML using our parser).

[qwerty]

It has its roots in Smalltalk. A lot of braces. Anyway it will get outdated and replaced by Swift in the next time (probably a couple of years).

q.

[OwenInCanada]

I'm not after the call graphs per se. My problem is a management problem.

A colleague, who reports to me, is writing an app in Objective-C, in XCode, on a MAC and using SVN. I am working on a Win7 box and have access to SVN: what tools can I use to review his progress and get a sense of the design?

For the record, we considered Swift and chose against it for this project.

I am more interested in actionable suggestions   , if you have any, than smart comments on my admittedly-somewhat-comical development environment  


Thanks and regards,

Owen

[qwerty]

Unfortunately there's not much help. Using XCode means you work completely in code. No UML, no nothing   I guess that setting up a parser for Swift would be a bit easier than for Obj-C but that wouldn't help you in your case anyway. May I ask in which area you develop that App so you someone on the Win-side is needed? I it just a parallel development on another platform so you need to know the structure?

q.

[OwenInCanada]

The problem is very simple: I don't own a mac.
Without a Mac I am more or less unable to supervise the development.
Swift would have been a more forward thinking choice I suppose, and i can't quite recall the rationale we used in not selecting it.
I am not working on that app development, my Win7 and linux environments support other projects - data analysis mostly.

[OwenInCanada]

Are there good static code analysis tools for Swift?

[qwerty]

Most likely not. Swift has been introduced to the public this autumn. They still have to cure quite some children sickness. The language itself is quite promising (though not mature as you might imagine). I think (!) that the code produced by the compiler is rather good. Apple spent a lot of money in developing Swift and it is announced to be the future development language. Just below it uses LLVM which isn't to bad too See here for a few details: http://nondot.org/sabre/

If you were just watching over the development just have them put the code into git (it's anyway integrated in XCode) and you can see the progress.

q.

[OwenInCanada]

Thank for your input.

Doxygen it is