From: Geoffrey F. <fu...@ga...> - 2002-01-21 22:08:43
|
I'm just a wee bit annoyed by the following: > /home/furnish> /lss/sw/fastflow/SuSE-7.2/bin/plrender > > Cannot open library file: drivers/drivers.db > lib dir="/lss/sw/fastflow/SuSE-7.2/lib/plplot5.1.0/data" > > No filename specified. > > Usage: > plrender [options] [files] > ... This was for a brand new checkout/build/install. The part I don't like, is the diagnostic about can't find "drivers/drivers.db", and the lib dir quote. I thought originally that probably this was some debugging output that I must've left around during the dyndrv merge without cleaning up, but now from my research with cvs log on plctrl.c, it looks like this has been there for years. What is new, is that in the dispatch init, we're effectively using pllibopen in a "try and see" semantic. What do people think? Should pllibopen really whine verbosely in a situation like this? Or should we shut off the warning? Or should we switch to pldebug or something like that? -- Geoffrey Furnish fu...@ga... |