[PATCH] Abstract out a display-table-specific API (2)

[mike.kupfer at xemacs.org]

>>>>> "ST" == Stephen J Turnbull <stephen at xemacs.org> writes:

ST> Make them defsubsts.  ;-)

ST> I'm not really joking about this case: I think it's a reasonable
ST> answer even though a bit fragile.  However, I acknowledge it's not a
ST> good generic answer.

I think a good generic answer would be to have 2 "futures" files: one
for compile-time fixups and one that's available at run time, probably
as part of xemacs-base.

How does that sound?

mike