But changing the SUBR signature did break it. Anyway, even since then, I am 
not confident that we have added only at the end, though I think everyone 
has tried to keep it that way -- only because I don't know if anyone tests 
this kind of compability, I haven't anyway.

----- Original Message ----- 
From: "Steven Yi" 
To: 
Sent: Thursday, March 31, 2005 10:52 AM
Subject: Re: [Cs-dev] plugins in cs4.23


> Modifying the ENVIRON struct doesn't break compatibility if thing are
> added at the end of the struct, if I remember correctly (we discussed
> this a couple years ago I think and I remember Michael Gogins
> explaining something like this to me at the time).
>
>
> On Wed, 30 Mar 2005 17:00:14 -0500, Anthony Kozar
>  wrote:
>> No, I have not changed any code to support opcode plugins (other than 
>> adding
>> the shared library loading stuff to dl_opcodes.c and that is in CVS). 
>> All
>> that I have done to make plugins work as expected is to create a symbol
>> export list in a file called Perf.cw4.mcp.exp.
>>
>> This file lists almost every non-static variable and function in global
>> scope in all of Csound (over 2000).  I removed a few names which were
>> troublesome or clearly not needed but most are there.  Yes, this means 
>> that
>> in Mills Csound you can do ridiculous things like call musmon() from a
>> plugin.  But I decided to err on the side of having too many exported
>> symbols since I had no idea (back then) which symbols were needed.
>>
>> In general, "SuperMills" contains very few changes to the cross-platform
>> Csound code and the Mills 4.23f12 release on Sourceforge is straight from
>> CVS.  Both support opcode plugins with all of the needed internal 
>> functions.
>>
>> I would suggest that something similar be done for GBS, MacCsound, 
>> MyCsound,
>> etc. unless there is no desire to really support plugins with these
>> "flavors" until Csound 5.
>>
>> I don't think that modifying the GLOBALS struct is a particularly good 
>> idea
>> though.  Since information about this struct may be compiled into 
>> existing
>> clients and plugins for Cs4, couldn't modifying the struct break them?
>>
>> Anthony
>>
>> On 3/29/05 8:13 AM, Victor Lazzarini  etched in
>> stone:
>>
>> > Following on from last week's discussion, I'd suggest that csdl.h, cs.h
>> > and oload.c in the 4.23 versions should be edited to provide a minimal
>> > interface for plugin
>> > opcodes, without which the whole thing is pretty much dead on the 
>> > ground.
>> > [...]
>>
>> > I suspect Anthony Kozar has done something of the kind so that
>> > plugins can work on SuperMills (not exactly sure if he made the same 
>> > changes,
>> > but they seem compatible to these).
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by Demarc:
>> A global provider of Threat Management Solutions.
>> Download our HomeAdmin security software for free today!
>> http://www.demarc.com/info/Sentarus/hamr30
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/info/Sentarus/hamr30
> _______________________________________________
> 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