https://bugs.documentfoundation.org/show_bug.cgi?id=154849
--- Comment #6 from [email protected] --- (In reply to Julien Nabet from comment #1) > … ask on dev mailing list Regarding communication, I did review of the developer documentation, mailing list archives, bugzilla issues (open & closed), and IRQ channels regarding the considerations for using Swift. My thinking to create an issue tracker ended up being to… 1. have a clear standalone thread on this particular topic 2. specifically create a single URL endpoint for this topic 3. avoid mailing list clutter and the transcient-ish nature of IRQ channels 4. provide a placeholder for any actions/tasks which may need to be done if proceeding forward (In reply to Michael Meeks from comment #4) > The question of whether it's a good idea to re-write existing working > Objective-C code into Swift is another one; Good question. In general, the leading champion of Objective-C (Apple) has been visibly moving away from Obj-C and decisively going with Swift since June 2014 (public release date)… nearly 9 years ago. In this specific case, I am looking to fix 3 bugs (not yet assigned) related to macOS specific printing NSPrintOperation/NSPrintPanel. This code has been broken as far back as 2014-05-19 (Bug# 78916). Long time broken and missing some fix'n. > and … people who step up and maintain that > piece of code would normally make that sort of decision. Yes. A code review is key. The expectation is that the Swift code will agreeably be, among other things, more readable and easier to maintain than the replaced Obj-C. Thanks for all your time and attention to this issue. --Marc -- You are receiving this mail because: You are the assignee for the bug.
