@wsfulton Hello, could you please review whether this version can be merged into the master branch

Hi @CancerQ. Thanks for updating this stale old branch. The original work was never merged to master because it was incomplete. In order to be considered for code review, can you please provide your thoughts on what still needs to be done according to the criteria for acceptance as outlined in https://swig.org/Doc4.2/Extending.html#Extending.

BTW, I've cancelled the last two builds running on CI, https://github.com/swig/swig/actions. You made 5 commits in one hour which resulted in 5 full builds of all languages. We need to be mindful of using up Github CI resources as each CI run uses a lot of compute. I suggest that once you've outlined what you plan to do to get this branch ready for review, you develop it in your own repo with CI turned off except for Objective C and post comments here with regard to progress.

@CancerQ please respond to my question from 3 weeks ago otherwise we will have no option to assume this is not a serious proposal to update and maintain ObjectiveC support in SWIG.

@CancerQ Do you still plan on working on this pull request, or would you prefer someone else take over?

@cancerq Please can you merge objective-c support in swig so we can make wrapper of ifc can you @programmingkidx or @Yize9 @wsfulton take over this is very important to have support for objective-c for using c library’s

@ojwb can you just review ago be according acceptable standards for master and then we would see what needed to be feature full

Sorry, I have very limited time available and I'm not going to waste it reviewing this further - it's been over a year since my initial review and nobody's even bothered to make the easy updates to address the problems I highlighted then.

There's clearly interest in having objc as a target language, but nobody wants to put in the hard yards to actually make that happen.

@wsfulton @ojwb can you run copilot on this files to see what he is thinking what is missing to align with missing elements from https://swig.org/Doc4.2/Extending.html#Extending , and second to take fast flight through code to correct old cvs stuff and depreciated macros and stuff to put this into master if there is a not lot of work 🙏💪

https://github.blog/changelog/2024-10-29-multi-file-editing-code-review-custom-instructions-and-more-for-github-copilot-in-vs-code-october-release-v0-22/

btw. If this is not in master people can’t use it and if can’t use it , we can see what missing or stuff which doesn’t work so can you put this into master as we say Minimum Viable Product (MVP) in agile.

Please stop @-mentioning me - that's just rude when nothing has actually changed here.

It's been clearly stated above what's needed from people wanting to progress this, so if you want it to progress please do that rather than creating noise which sucks up more of my very limited time for working on SWIG.

We need a new target language to achieve certain targets before it can be merged based on past experience of merging half-written target languages and that working out badly.

If people want to try out the work in progress they can check out the PR branch and build that - it shouldn't really be any different to building the main branch.