How to become a member ?

mulle-nat commented 7 years ago

Comment in this thread and you will be sent an invite to the mulle-objc organization. By default github will make you a private* member. But only public members are useful to the project and will get an invite to the mulle-objc slack*.

How to be come a public member

To become a public member, after becoming a regular member, visit https://github.com/orgs/mulle-objc/people. Look for your name in the first column, and in the third column change your security setting from private to public. Done!

screeny

If your email-address is not in your public github profile, send it by email to nat-github-slack@mulle-kybernetik.com. Your email address is needed for the Slack invite.

Official Github instructions how to become a public member.

And here is a "how to" with more detail:

An email with the invitation will be sent by github. In the email their will be a link. Be sure to be logged into github before clicking the link. Then click the link. You should see something like this:

You can also periodically visit mulle-objc to see, if you got an invite. Then it should look like this:

where the button leads you to the invitation page.

Markers

The membership processing status can be seen from your posts markers:

Marker	Meaning
❤️	Member invite sent
🎉	Member invite resent
👍	Slack invite sent

Markers may not be visible on the mobile version of GitHub

If you expect an invite for membership or slack access, but haven't gotten one yet: just email me or post again in this thread.

mulle-nat commented 3 years ago

Sure but a separate issue would be good. I tried to move it, but failed somewhat :)

alepi commented 3 years ago

I'd like to get the invite as well if possible. That's why I also commented here :-)

mulle-nat commented 3 years ago

@alepi if you want an invite for Slack send me an email to nat-github-slack@mulle-kybernetik.com

ghost commented 2 years ago

Hello, could I join your project? I am currently working on a SAS compiler and am looking at Objective-C as an upgrade to the C code I am working with, and am excited to see where mulle-objc will go.

mulle-nat commented 2 years ago

Sure ;) What's SAS ?

ghost commented 2 years ago

Sure ;) What's SAS ?

Thank you for the invitation! SAS is a programming language used for statistics, in a similar vein as the R language.

minusbat commented 2 years ago

OK, I am amazed, and delighted to find this! I thought I was the last person left on the planet who was using Obj-C outside of an Apple environment. I wrote my own basic set of objects many years ago, as I ended up in a job where I needed to deploy on NT4 using whatever language I liked, but I wanted to develop on BSD. So I hacked together an object/string/array/dictionary and uses gcc on both platforms, and have never looked back.

That was 1999, and I am still running it and it keeps me in a job ;) These days its using clang and the libobjc2 runtime. But I am now excited by the idea of porting to this runtime instead.

Is there a mailing list somewhere, or some kind of community ? I dont have time to experiment today, (I only found this an hour ago), but hope to try some things out over the next few days if I can. This looks brilliant!

mulle-nat commented 2 years ago

Cool! I guess yours it not open source ? I didn't see anything on your account. Other Objective-C libraries are always interesting to look at.

The community is here basically. There is no mailing list, but there is a "Slack", which is very quiet. In terms of getting help or feedback, you can try various channels, like github issues on any related project, Slack posts, emails to me. To get access to Slack you got to run through the low-obstacle course pointed out in the first post.

Just in case things don't work out, negative feedback would also be appreciated. Maybe even more appreciated, than positive feedback, because I already know that it's good :laughing:.

minusbat commented 2 years ago

Oh, it's open source, and you can get it here if you want to take a look...

git://toybox.twisted.org.uk/pfkit

Am slightly cringing at the idea of someone seeing that code however :-)

[ I originally wrote it back in 1999, so it was under RCS, and later SVN. I did give it out on mailing lists a couple of times. But as its pretty specialised to me (and even more so 23 years later) then I never really made a thing of it. I did make a git repository though, as it makes it easier for work, and that's what the link is above. ]

So, yes, I shall have a go with your runtime as soon as I get some spare time, and shall give you feedback! Is it a drop-in replacement for libobjc2, or will I need to tweak some calls ? Am assuming the latter, plus I also note you seem to have your own fork of clang ? Do I need to use that ?

Anyway, thanks for the fast reply!

mulle-nat commented 2 years ago

Am slightly cringing at the idea of someone seeing that code however :-)

It's too late now :smiley:... but it looks good to me.

Is it a drop-in replacement for libobjc2, or will I need to tweak some calls ?

It's way different. But there is a compatibility layer, which could be helpful here, that adapts a lot of the apple runtime functions like objc_msg_lookup.

Am assuming the latter, plus I also note you seem to have your own fork of clang ? Do I need to use that ?

I think yes, otherwise it's going to be too much effort. Looking at your code, there are three ways to do it I think:

replace all libobjc function calls with mulle-objc-runtime equivalents (hard)
use mulle-objc-compat for runtime function calls, code around places where there is no match (could be easy to hard)
use MulleObjC and substitute PFObject with NSObject, then put missing PFObject methods into a NSObject( PFObject) category (easy)

minusbat commented 2 years ago

Am glad it didn't horrify you too much ;) Ok, I will start by downloading and building your clang fork then. I found your compatibility layer (option 2) and thought that would be a good start too. Ideally I would ut n the effort to go fully option 1 though.

Option 3 is interesting. The problem might be the 300,000+ lines of commnercial code which sits on top of all of this, and which might have dependencies on odd behaviours of my PFObject that I am unaware of (I wrote all of that too, its been a long 23 years).

But I shall start with the compiler and see what I can get running... thanks for the tips!

mulle-nat commented 2 years ago

Yeah, good luck! I think in terms of highlevel runtime differences, there are two things to keep in mind.

the mulle-objc-runtime was written to be lock free and wait free, this isn't super-true anymore due to the way +initialize works. Yet: one of the consequences of the design are, you can only add methods and classes, you can not remove anything.
the mulle-objc-runtime uses the metaABI for method calls. So doing method calls "outside" of the mulle-clang compiler for example using IMP is very different.

Hit me up anytime something comes up.

mulle-nat commented 2 years ago

@minusbat So how did it go ? I assume there were no problems, since I didn't hear anything :smile:

strojacek commented 2 years ago

Hello, if you are still accepting members, could I join the group?

mulle-nat commented 2 years ago

Sure thing. An invitation should be at your doorstep.

stianhoiland commented 2 years ago

This project is amazing, wow! You're a wizard, mulle. Please send me an invite to join :) As an aside: Would you consider bridging the chat to Discord?

mulle-nat commented 2 years ago

Thanks for the kind words. An invite has been sent. I would consider bridging the Slack to anything, but there is just not enough traffic there to make it worthwhile the effort.

stianhoiland commented 2 years ago

Getting a Discord server up would lower the bar for initiating contact, potentially on-boarding fence-sitters. And can I just say, this project needs more attention.

Also, I've done the public member dance thingy. waits impatiently

mulle-nat commented 2 years ago

The Slack invite has been sent a few hours ago, since you are waiting impatiently, you may want to check your SPAM folder :smile: