Actually, thinking about it more I think I would be ok with selective usage of ARC in new files. Again, maybe chat with me first, as I'm curious what the use case is, and autorelease works differently between ARC and manual.
On Sun, Sep 13, 2020 at 2:54 AM Yee Cheng Chin <ychin.mac...@gmail.com> wrote: > Actually, MacVim uses new APIs all the time! For example, it supports > Touch Bar which requires 10.12.2. Features that use these newer APIs do > have to be optional with the correct compile-time and runtime checks, > unless we make a conscious decision to update the minimal target (10.9). To > be fair, MacVim is not actively tested on older macOS versions like 10.9, > and so we would only know of issues if people file bugs against MacVim. > > I'm curious what you intend to use NSStackView for though? If it's a major > feature, you may want to file a WIP PR/issue or contact us first just to > get some feedbacks. MacVim's philosophy is to be the most integrated / > native gVim implementation on macOS, and intentionally not bloated with > non-Vim features, so I'm curious what feature would need NSStackView. > > ARC: It's mostly legacy. Developers' time is limited, and I think it's > better to spend time on implementing other features / fixing existing bugs > than converting to ARC. If you want to write new code, please use the > existing memory allocation mechanism instead of ARC. The reason is the same > as why companies have coding standards: inconsistencies in the codebase > tends to be worse than whatever problem you are trying to fix. > > Thanks for contributing! > > On Sat, Sep 12, 2020 at 8:24 PM sam <sanja...@gmail.com> wrote: > >> A couple questions about MacVim development: >> >> The current release (snapshot 165) of MacVim targets macOS 10.9+. Does >> that mean that new code can use any Cocoa API from macOS 10.9 or before? >> For example, NSStackView was introduced in macOS 10.9. MacVim doesn't >> currently make use of this API, but if a potential contributor wanted to >> work on a feature, could they use it? >> >> It also appears that MacVim does manual memory management. ARC was >> introduced well before macOS 10.9. Could new code use ARC if it is in its >> own file and compiled with the fobj-arc flag? Is there a reason not to >> migrate MacVim to ARC? >> >> -- >> -- >> You received this message from the "vim_mac" maillist. >> Do not top-post! Type your reply below the text you are replying to. >> For more information, visit http://www.vim.org/maillist.php >> >> --- >> You received this message because you are subscribed to the Google Groups >> "vim_mac" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to vim_mac+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vim_mac/37b2f7a4-322c-42e9-9157-e2c68222d061n%40googlegroups.com >> <https://groups.google.com/d/msgid/vim_mac/37b2f7a4-322c-42e9-9157-e2c68222d061n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- -- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_mac" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_mac/CAHTeOx_d8XV%3DkCjEbLm%3D2s0YRbeN3MVjrSMYjm_htevvbo-zMQ%40mail.gmail.com.
