Hi.

I'm assuming that a new SDK will be released to work with Objective-C?
Or should that work with the 3.10 SDK already combined with MorphOS 3.10?


Manfred

I am hoping to release the 3.12 SDK within a month or two. The ObjC will be unavailable to 3rd party programmers till then.

[ Edited by jacadcaps 26.03.2018 - 18:58 ]

Does the SDK only contain the Foundation classes or also GUI bindings with nib file support?

Quote:

There is no nib support since there's no Cocoa.

We'll publish an article on this soon which I think will answer most questions.

Really cool. I like Objective C.

Is the eventual goal to replace GCC with Clang?

Quote:

For entire MorphOS you mean? That sounds unlikely. We're currently using gcc 2, 4, 5, 6 and clang to build MorphOS :) It'd be a nightmare to port everything...

Quote:

Yeah that's what I meant and it most likely being a nightmare was why I asked. :)

Does a MorphOS port of Clang exist behind closed doors now or only a cross compiler?

Quote:

We have both variants. Will be included in the next SDK.

Quote:

We could probably have let gcc4 die a long time ago though, I'm guessing it's mainly due to "lazyness" that we still have things built with it. :)


- CISC

Will there also be more features supported for C++ 11 like threading?

Quote:

We generally add these things as we go along (as in, when something we're doing requires it). Threading should be supported, at least to a degree, if I remember right.

Quote:

Great news, I look forward to it. Thanks. :)

May be a little bit off-topic but gcc 7 behaves really well on ppc. I can tell that from running/building Gentoo Linux with it. Even Firefox got much less bitchy.

Seems the new register allocator gcc 7 uses for ppc is some good: https://gcc.gnu.org/gcc-7/changes.html

Quote:

Nib files are not Cocoa. GNUstep also uses nib in Project Builder.
But the article answers everything

Just posting the link to the article here as a reference for people who find this discussion but might miss the news post:

morphos-team.net/guide/objective-c

Is there support for XCTest? Or the older SenTestingKit?


Manfred

Quote:

Nope. Maybe in the future...

Quote:

So you're developing Iris without unit tests?

Quote:
Show me project for MorphOS/AmigaOS which is developing with unit tests. :)

I think we have more important issues than no unit tests. Jaca is one man, not a corpo dev-team. :)

Quote:

That's unfortunately the usual thinking.
We're in the 21st century.

It's a common misconception to think that developing test driven takes more time than without.
On the contrary. In the big scheme you safe yourself a lot of time and grey hair. It gives you confidence that your code still works after you have done major refactorings.
Because if you have a good coverage you click a button and 5, 10 or 15 minutes later you know if you can release or not.
Otherwise how much time do you spent going through all the manual tests again and again and again. What a pain.
Test driven development is done (or not done) by individuals, small teams and large teams. The number of people involved is irrelevant.


Porting XCTest would have been one of the first things I had done.

And yes, unit tests are not seen often in Amiga world.
Probably because the tooling is not convenient enough. Or no one actually knows how to do it. I don't know.
But MorphOS is powerful enough to support that. And in XCTest there is a nice unit test framework.
When the SDK is there I'd have a look at porting it.

[ Edited by asrael22 30.03.2018 - 17:40 ]

Quote:
full ack!
This is not native software but even the SGML documentation is validated

I actually do have some test apps (for Iris functionality testing) but as a whole I am not writing unit tests since these are boring :)
This is done in my spare time when I want to relax and maintaining unit tests is not relaxing for me.

Quote:

Yeah, people are different.
I find great joy starting with writing tests on a small unit and see how gradually the code builds up. :)
It's also that the structure of your code is different when you write unit tests. Code that must be testable must be structured differently.
But even if you do this in your spare time, you want to produce value for users and for yourself.

Quote:

The ob.framework does have unit tests by the way - mostly due to the fact that when I was buildig it there were no real apps to test this. With mui.framework I was actually writing the new LogTool application in parallel to see if the ideas make sense...