On Tue 30 Mar 2010 23:52, l...@gnu.org (Ludovic Courtès) writes: >>> And we could add a ‘public-interface’ slot to ‘module-type’ and have >>> ‘module-public-interface’ and ‘set-module-public-interface!’ refer to >>> it; for backward compatibility we’d also initialize the >>> ‘%module-public-interface’ binding. How does it sound? > > Actually the trick wouldn’t work in cases where the > ‘%module-public-interface’ binding is mutated, as with Lilypond. > > Given this and the above examples, I’d suggest dropping that binding > completely and sending patches to the Lilypond/TeXmacs people.
Hm. I guess you're right. In the case with deprecated foo enabled, we can add a %module-public-interface definition in the root module, which maps to a module with a binder procedure that will raise an error. That way we can catch apps that we don't know about. Andy -- http://wingolog.org/
