On Wed, 2003-09-03 at 09:38, Raymond Toy wrote: > >>>>> "Gerd" == Gerd Moellmann <[EMAIL PROTECTED]> writes: > > Gerd> Craig Lanning <[EMAIL PROTECTED]> writes: > > >> > [thanks for the patch, any idea when this patch will show up in a > >> > release?] > > Gerd> Well... The question is when a new version will be released. > Gerd> I think there's an agreement among developers that a 19a should > Gerd> be released soon, but the value of soon hasn't been determined yet :).
I hope the value of soon is small. > >> > > >> > On a different note: You mentioned a warning that would like to get > >> > rid of. Could you please try to make a simple test case for that? > >> > >> I didn't mean a single warning. > >> > >> This application generates and loads a lot of interpreted lisp code. > >> Each time it does CMUCL compiles that code as it loads. The compiler > >> produces a lot of warnings about the code that is being compiled. I > >> just want to suppress those warnings so that they don't clutter the > >> output from the application. > > Gerd> Hm, maybe you are looking for > > Gerd> (declaim (optimize (ext:inhibit-warnings 3))) > > Gerd> ? Dunno. > > But this hides everything. That's the idea. Unfortunately, (ext:inhibit-warnings 3) didn't hide enough. I'm still seeing these: ; Note: Ignoring free ignore declaration for PCL::.METHOD-ARGS.. ; ; Note: Ignoring free ignore declaration for PCL::.NEXT-METHODS.. > I'd go for doing that in just the > functions where I know the notes are unimportant. > > If they're warnings, then I'd be careful about turning off all the > warnings. I just want to be able to turn them off for users. The presence of the warnings doesn't help them any and makes the output of the application very difficult to find. > You can also send the output to a file so you don't see them unless > you want to. In some modes, the app sends its output to files. Craig
