Sorry, I wasn't thinking, there's a much cleaner solution. Never mind.

Brad

On Mar 4, 2015, at 12:19 AM, Bradley Lucier lucier@math.purdue.edu wrote:

Marc:

I've got ##wr-meroon going pretty well, but if Meroon isn't loaded, then I get the following warnings when I use certain Meroon functions (obviously):

*** WARNING -- "Class-fields" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "Class-name" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "Field-name" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "Mono-Field?" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "field-defined?" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "field-length" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "field-value" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "object->class" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c")

I figure I can get around this by defining non-block dummy procedures for these Meroon-defined functions that will be replaced when Meroon is loaded. Perhaps you have a better solution.

But is it possible to tell dynamically whether Meroon (or _meroon.o1, or whatever) has been loaded?

Brad