I think we probably need to define then an opcode
development API, granting access to memory management
stuff, as well as function table access and possibly
a few things more.

Victor

 
> none.  thats what the API is for!
> 
> On Mar 27, 2005, at 10:25 AM, Anthony Kozar wrote:
> 
> > Which symbols does/should Csound 4 export?  It is
> > clearly necessary to export more than just the API
> > calls.  (On MacOS 9, to make life easy, I export almost
> > every non-static global in Csound -- bad, I know, but it
> >  was expedient and I never have linking issues).
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products
> from real users. Discover which products truly live up to
> the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Csound5's API has much more in it than Csound4's.  As Matt pointed
out, no opcode lib should use anything but the API.  CS5 has functions
for allocating memory and most anything that an opcode would need, and
if it doesn't, adding new API functions should be discussed and
considered for addition.

steven


On Sun, 27 Mar 2005 21:21:42 +0100, Victor Lazzarini
 wrote:
> I think we probably need to define then an opcode
> development API, granting access to memory management
> stuff, as well as function table access and possibly
> a few things more.
> 
> Victor
> 
> 
> > none.  thats what the API is for!
> >
> > On Mar 27, 2005, at 10:25 AM, Anthony Kozar wrote:
> >
> > > Which symbols does/should Csound 4 export?  It is
> > > clearly necessary to export more than just the API
> > > calls.  (On MacOS 9, to make life easy, I export almost
> > > every non-static global in Csound -- bad, I know, but it
> > >  was expedient and I never have linking issues).
> >
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products
> > from real users. Discover which products truly live up to
> > the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
> click
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

We are all waiting for more examples, project files, and a tutorial on how
to add opcodes to MacCsound!  I would love to publish this in my new book
(Matt? Victor), in addition to exploring these possibilities with my
students at Berklee and NYU.

Dr. B.

on 3/27/05 3:21 PM, Victor Lazzarini at victor.lazzarini@nuim.ie wrote:

> I think we probably need to define then an opcode
> development API, granting access to memory management
> stuff, as well as function table access and possibly
> a few things more.
> 
> Victor
> 
> 
>> none.  thats what the API is for!
>> 
>> On Mar 27, 2005, at 10:25 AM, Anthony Kozar wrote:
>> 
>>> Which symbols does/should Csound 4 export?  It is
>>> clearly necessary to export more than just the API
>>> calls.  (On MacOS 9, to make life easy, I export almost
>>> every non-static global in Csound -- bad, I know, but it
>>>  was expedient and I never have linking issues).
>> 

_______________________________________________________________________
 +  Dr. Richard Boulanger, Professor
 +  Music Synthesis Department, Berklee College of Music
 +  1140 Boylston Street  - Boston, MA  02215-3693
 +  Office Phone: (617) 747-2485   Office Fax: (617) 747-2564
 +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
 +  WebPage: http://csounds.com/boulanger/
________________________________________________________________________
 +  Almost Everything Csound @ http://csounds.com/
 +  The Csound Catalog with Audio @ http://csounds.com/catalog/
 +  The Csound Book @ http://csounds.com/book/
 +  The Csound Magazine @ http://csounds.com/ezine/
 +  CsoundForums @ http://csounds.com/phpBB2/
________________________________________________________________________



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

might make things a bit easier.. there are definitely
some functions that should only be needed by hosts and some only
needed by plugins..   i do seem to remember previous discussions
about this..

On Mar 27, 2005, at 12:21 PM, Victor Lazzarini wrote:

> I think we probably need to define then an opcode
> development API, granting access to memory management
> stuff, as well as function table access and possibly
> a few things more.
>
> Victor
>
>
>> none.  thats what the API is for!
>>
>> On Mar 27, 2005, at 10:25 AM, Anthony Kozar wrote:
>>
>>> Which symbols does/should Csound 4 export?  It is
>>> clearly necessary to export more than just the API
>>> calls.  (On MacOS 9, to make life easy, I export almost
>>> every non-static global in Csound -- bad, I know, but it
>>>  was expedient and I never have linking issues).
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products
>> from real users. Discover which products truly live up to
>> the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
> click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

as far as im concerned the plugin support should be considered  
preliminary
until maccsound supports cs5.

but regardless, it should be the same as  tutorial/documentation
on any other ( csound4 ) platform

-m

On Mar 27, 2005, at 1:43 PM, Richard Boulanger wrote:

> We are all waiting for more examples, project files, and a tutorial on  
> how
> to add opcodes to MacCsound!  I would love to publish this in my new  
> book
> (Matt? Victor), in addition to exploring these possibilities with my
> students at Berklee and NYU.
>
> Dr. B.
>
> on 3/27/05 3:21 PM, Victor Lazzarini at victor.lazzarini@nuim.ie wrote:
>
>> I think we probably need to define then an opcode
>> development API, granting access to memory management
>> stuff, as well as function table access and possibly
>> a few things more.
>>
>> Victor
>>
>>
>>> none.  thats what the API is for!
>>>
>>> On Mar 27, 2005, at 10:25 AM, Anthony Kozar wrote:
>>>
>>>> Which symbols does/should Csound 4 export?  It is
>>>> clearly necessary to export more than just the API
>>>> calls.  (On MacOS 9, to make life easy, I export almost
>>>> every non-static global in Csound -- bad, I know, but it
>>>>  was expedient and I never have linking issues).
>>>
>
> _______________________________________________________________________
>  +  Dr. Richard Boulanger, Professor
>  +  Music Synthesis Department, Berklee College of Music
>  +  1140 Boylston Street  - Boston, MA  02215-3693
>  +  Office Phone: (617) 747-2485   Office Fax: (617) 747-2564
>  +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
>  +  WebPage: http://csounds.com/boulanger/
> _______________________________________________________________________ 
> _
>  +  Almost Everything Csound @ http://csounds.com/
>  +  The Csound Catalog with Audio @ http://csounds.com/catalog/
>  +  The Csound Book @ http://csounds.com/book/
>  +  The Csound Magazine @ http://csounds.com/ezine/
>  +  CsoundForums @ http://csounds.com/phpBB2/
> _______________________________________________________________________ 
> _
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real  
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net