Open tgrey1 opened 4 years ago
imo i don't think it needs a separate manual page as includestr is already mentioned in the Syntax, as well as the remark: #includestr is similar to #include except that the file name must be delimited by a double quote character and the file name is subjected to macro expansion.
Also, it is mentioned separately n the list overview of the Orchestra Macros https://csound.com/manual/OrchMacros.html
What could help exposing this variation on #include further, is an example of #includestr on the manual page?
More examples are always helpful.Dr. Richard BoulangerProfessorElectronic Production and DesignBerklee College of MusicOn Jun 14, 2024, at 1:38 PM, Menno Knevel @.***> wrote:
imo i don't think it needs a separate manual page as includestr is already mentioned in the Syntax, as well as the remark:#includestr is similar to #include except that the file name must be delimited by a double quote character and the file name is subjected to macro expansion. Also, it is mentioned separately n the list overview of the Orchestra Macros https://csound.com/manual/OrchMacros.html What could help exposing this variation on #include further, is an example of #includestr on the manual page? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
currently includestr is a footnote on include's page. this probably deserves it's own entry page and example.
if it gets it's own page: