3 ms·
But like I said, it depends on what the code is. If it's a kernel module, then you'd be silly not to use the gcc extension. Likewise if it's a platform-locked
by ajross 15y ago
But like I said, it depends on what the code is. If it's a kernel module, then you'd be silly not to use the gcc extension. Likewise if it's a platform-locked linux or mac thing (Android middleware, maybe). You work in security, where you're expected to port stuff between platforms regularly. Not everyone does. And those extensions are there because someone likes them.
- dap 15y ago> If it's a kernel module, then you'd be silly not to use the gcc extension. Sure, if you're not interested in anyone porting that code to another OS. This happens all the time with drivers -- just because the interface is OS-specific doesn't mean all the code is. > And those extensions are there because someone likes them. That doesn't make it a good idea.
- mansr 15y agoExtensions have occasionally been dropped from gcc, sometimes because of conflicts with updated standards, sometimes for other reasons.