On Mon, Jan 24, 2022 at 08:14:31PM +0000, Peter Maydell wrote: > On Mon, 24 Jan 2022 at 17:49, Roman Bolshakov <ro...@roolebo.dev> wrote: > > I'm not sure why blocks are Objective-C specific. All the data I have > > shows the opposite [3][4][5]. They're just extensively used in Apple APIs. > > This is true, but for the purposes of our build machinery it is > simpler to have three types of source files that it deals > with (C, C++, ObjC) rather than four (C, C++, ObjC, C-that-uses-blocks). > So unless there's a clear benefit from adding the extra category > I think we should do the simple thing and keep these files named > with a ".m" extension. >
Fine by me as long as majority finds it's simpler :) Perhaps it's just a matter of personal preference. I've used to the fact that platform-specific code uses platform-specific extensions or some sort of weird "GCC attributes". Therefore C with an extension is easier to reason for me than Objective-C with ARC and other kinds of implicit behaviour without an actual Objective-C code. Thanks, Roman
