[CM] TRACE facility seems broken in 22.5

[David O'Toole]

For example if I deliberately pass:
> >(save-sound-as "/home/dto/foo.snd" ())

I get:

save-sound-as second argument, (), is nil but should be a sound object, an
integer (sound index), or #f

This is why I was asking what conditions could cause "save-sound-as" to
simply print its name and fail

On Tue, Jul 12, 2022 at 4:54 PM David O'Toole <deeteeoh1138 at gmail.com>
wrote:

> Actually, the output I gave is not from the trace feature, as it appears
> whether or not the function is traced.
> So I don't know if it actually signifies that the sound passed was ().
> I put in (assert (sound? some-sound)) and it doesn't complain.
> I'll investigate more.
>
>
> On Tue, Jul 12, 2022 at 4:36 PM David O'Toole <deeteeoh1138 at gmail.com>
> wrote:
>
>> Oh, I must have messed up something. I'll investigate further. Thank you!
>>
>> On Tue, Jul 12, 2022 at 4:15 PM <bil at ccrma.stanford.edu> wrote:
>>
>>> It looks like some-sound is () which will cause save-sound-as
>>> to raise an error.  If the error isn't caught, it will
>>> cause the loop to stop and will return to the top level.
>>> I'm guessing the output is from trace as the function is
>>> entered, then you hit the error, and the current evaluation
>>> is stopped.  () is an error because it does not identify
>>> the sound you want to save.
>>>
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20220712/087d6ec1/attachment.html>