This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] Deprecate XM_FILE and TM_FILE

Calling something ``deprecated'' means that it will go away in a
future release.   When XM_FILE goes away, xm-go32.h will no longer be
doing its job, and the DJGPP port of GDB will be severely broken.

> Therefore, deprecating XM_FILE means you are deprecating the DJGPP
> port.

Eli, sorry I'm still lost.

Here, the xm-go32.h file will have been removed before the XM_FILE mechanism goes away (if it hasn't we've both seriously fallen down on the job :-) and therefore, DJGPP won't be broken. In fact, thanks to Joel's and MarkK's efforts, we're even ahead of schedule on this one!

This is all about preventing new uses of an old mechanism that we're trying to replace, not about deprecating DJGPP.

Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]