I also think that the performance impact will be small. So, I will rework the macro as per Nathan's suggestion. But should maintainers  go one step ahead and clean the entire SBCL sources from 'high-security' feature expression at all? Or it is useful in some situations?

Regards,
Roman


2010/5/29 James Y Knight <foom@fuhm.net>
On May 28, 2010, at 4:52 PM, Nathan Froyd wrote:
On Fri, May 28, 2010 at 3:44 PM, Roman Marynchak
<roman.marynchak@gmail.com> wrote:
 I have seen this feature expression in several source files, for example in
/code/sysmacs.lisp:

It seems that it is some old CMUCL feature expression. Is it okay to get rid
of it, at least in that macro? I need the stream type check to be made by
default in order to fix this issue:

https://bugs.launchpad.net/sbcl/+bug/586940

The first step is to pass t as a second macro argument, and the second is to
remove or enable 'high-security', as one may guess from PRINT definition:

The second macro argument seems to be totally unused, so it's probably
best to just delete the argument from the macro and make the check the
default.

I suppose it was omitted because of the performance cost? Although, checking the type of an argument can't *really* have significant performance cost in an output function I wouldn't think.

James