Masterscope: . ANALYZE filename fails silently

[hjellinek]

The Masterscope command

. ANALYZE filename

fails silently.

The corrected command

. ANALYZE ON filename

works as expected.

[rmkaplan]

Perhaps . ANALYZE filename should at least print a message “filename is not a function” ?

…

On Oct 23, 2024, at 2:23 PM, Herb Jellinek ***@***.***> wrote: The Masterscope command . ANALYZE filename fails silently. The corrected command . ANALYZE ON filename works as expected. — Reply to this email directly, view it on GitHub <#1858>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJLB2JKABLWNCGX3SC3Z5AHVLAVCNFSM6AAAAABQPWS7QGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYDSOBXHA3TCMI>. You are receiving this because you are subscribed to this thread.

[MattHeffron]

This looks like a job for DWIM!

[rmkaplan]

No, what if you have a function and a file with the same name? The syntax for functions and files is different—files require ON. If you say . ANALYZE ON XXX, you get a file-not-found error. By symmetry you should get a meaningful message or error if you say . ANALYZE XXX, where XXX is not a function.

…

On Oct 23, 2024, at 4:16 PM, Matt Heffron ***@***.***> wrote: This looks like a job for DWIM! — Reply to this email directly, view it on GitHub <#1858 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJIO6ZCOUK7RMJ7YZGLZ5AU6LAVCNFSM6AAAAABQPWS7QGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZTG42TMMBSGQ>. You are receiving this because you commented.