[m-dev.] Re: conditional compilation

Paul Bone pbone at csse.unimelb.edu.au
Tue Jan 5 20:23:28 AEDT 2010

On Tue, Jan 05, 2010 at 07:26:10PM +1100, Peter Wang wrote:
> On 2010-01-05, Paul Bone <pbone at csse.unimelb.edu.au> wrote:
> > On Tue, Jan 05, 2010 at 05:41:08PM +1100, Peter Wang wrote:
> > > 
> > > With conditional implementation sections I could cleanly separate the
> > > two completely different implementations, while providing the single
> > > module interface.
> > 
> > An extra benefit that we can get here is that the 'disabled' sections can be
> > error checked but not compiled.  This can help us verify that these sections
> > are correct even when they aren't applicable to the current backend/platform.
> Actually, probably not.
> You could possibly tell the compiler about different grade and trace
> flag combinations that you want to check, but you could already do that
> by running mmc --make foo.errs with different options.  I wouldn't want
> to clutter up the compiler source with it.

Sure, it probably makes more sense when considering decisions that the front
end of the compiler will make for different grades.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/developers/attachments/20100105/0f9c1d5c/attachment.sig>

More information about the developers mailing list