Platform-Specific Extensions (was Re: [GUI] Dynamic sizing.)

Wolfgang Thaller wolfgang.thaller@gmx.net
Mon, 28 Apr 2003 14:27:30 +0200


> On Sun, Apr 27, 2003 at 09:14:16PM +0100, Glynn Clements wrote:
>>> 2) Such platform-specific functions must be clearly marked as such.
>>> I suggest that we follow the example of OpenGL and mark extensions
>>> using a suffix to the name, e.g.
>>> mkXmForm_EXT, loadNibFile_EXT, etc.
>>
>> I'd rather just use modules and qualified names.

It's probably the more Haskell-like way. Should be fine as long as we 
stay away from adding constructors to datatypes (which we probably 
should anyway).

Axel Simon wrote:

> Me too. We might even use the deprecated pragma (or something similar) 
> to
> flag if the user uses backend specific functions.

I wouldn't like that, because it would give me tons of warnings for 
perfectly good platform-specific programs. Just tell users to always 
import the "extensions" modules qualified, and no-one will ever use an 
extension without knowing it.

Cheers,

Wolfgang