I am revising a draft of my being tested quark. I would like to have the method cpsoct in this Quark which overrides the built-in core method cpsoct. When evaluating MethodOverride.printAll after recompiling the sc libraries after adding the following line in a SC file in my Quark:
there are the following lines where sclang returns in the post window:
Overwritten methods in class library:
-------------------------------------
SimpleNumber
------------
SimpleNumber:cpsoct
/Users/prko/Library/Application Support/SuperCollider/downloaded-quarks/Notator/Classes/SPN.sc
/Users/prko/Dropbox/prko/__myDocs/Writings/Making Sound using Open Sources/mixed/dev - Bleeding edge/SuperCollider.app/Contents/Resources/SCClassLibrary/Common/Math/SimpleNumber.sc
However, when evaluating the following code:
440.cpsoct
the built-in core method is still applied and my quark does not affect it.
How could I override a built-in core method using quarks?
WARNING: Extension in '/Users/prko/Library/Application Support/SuperCollider/downloaded-quarks/Notator/Classes/SPN.sc' overwrites SimpleNumber:cpsoct in main class library.
Intentional overwrites must be put in a 'SystemOverwrites' subfolder.
I also found the following warning
I did not know where the SystemOverwrites folder was. Using the Finder’s ‘Find’ feature, I was able to understand how to save this part. Currently, the part I asked about in the previous post is stored in /Users/prko/Library/Application Support/SuperCollider/downloaded-quarks/Notator/Classes/SystemOverwrites/syntactic_sugar_SPN.sc. There is no warning anymore, but the method I want to use is still unaffected, but the built-in core method of SimpleNumber is affected.
The method I made is very similar to the built-in method and has only a short explanation before output, so I think my method can replace the built-in method for future users of my Quarks, if any. However, it seems better to use a different method name.