Csound can indeed currently be compiled with MSVC, CsoundAC cannot (thanks 
to limitations on the MSVC implementation of the Standard C++ Library in 
dynamic libraries).

Regards,
Mike

----- Original Message ----- 
From: "Pinball" 
To: 
Sent: Sunday, February 08, 2009 6:17 AM
Subject: Re: [Cs-dev] some ideas for Csound 6


>
>
>
> Anthony Kozar-2 wrote:
>>
>> Yes, this kind of separation could be very good for Csound in the long
>> run.
>> I am a little worried that the temptation to take the most expedient 
>> route
>> will drive us to implement major new features such as the dynamic
>> instrument
>> loading in a "hackish" manner without significantly modifying the current
>> internals.  Doing a thorough refactoring could take a long time.
>>
>> I am sure that there are other features that people would like to add 
>> that
>> belong properly to "Csound 6" because they will require significant API
>> changes, but that may take much less time than a full refactorization.  I
>> am
>> guessing that John brought up the Channels API question the other day
>> because he was actually ready to sit down and start changing it.  I don't
>> know how we should plan to accommadate both short and long term API
>> changes.
>>
>> A clear roadmap for Csound 6 -- and possibly Csound 7 -- would give us
>> something to work towards and would allow developers to make choices 
>> about
>> the best use of their time.
>>
>> Any suggestions?
>>
>
> A)
>
> Short term changes in CSound 5.xx
> (Not so) Long term changes in CSound 6.xx
> INSTRs vs UDOs in CSound 7.xx
>
> ?
>
>
> B)
>
> I also wish CSound could be compiled with MSVC++
>
>
> C)
>
> 1) The instrument source (a text file)
> 2) The instrument code (bin file)
> 3) The orchestra source (a collection of instruments sources)
> 4) Whatever source
>
> will all translate into Instrument Data (IDATA) (the bin file
> itself ?). An Instrument Data Format (IDF) must be defined.
>
> So, independently of the sources, the csPerformer will play
> a chain of IDATA chunks at k-time, running the opcodes each
> IDATA is associated with.
>
>
> What will the Instrument Data Format look like? A chunk of
> memory with a list of opcodes followed by in/out argument
> references? It should be stored and loaded later, eventually
> resolving the opcode addresses and arguments (instances)
> Where in memory are the arguments stored? What about
> arguments tables?
>
>
> -- 
> View this message in context: 
> http://www.nabble.com/Channels-tp21852607p21897809.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with 
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code 
> to
> build responsive, highly engaging applications that combine the power of 
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK 
> and
> Ajax docs to start building applications 
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

michael.gogins wrote:
> 
> Csound can indeed currently be compiled with MSVC, CsoundAC cannot (thanks 
> to limitations on the MSVC implementation of the Standard C++ Library in 
> dynamic libraries).
> 

I wanted to try to build a project from scratch,
the DLL only, adding the required *.c and *.h
files, fixing what was missing (looking at the 
makefile provided). I didn't want to use mingw
or scons or whatever.

The compiler didn't seem to find the "f math"
functions (powf and so on) when the sources
extension was ".c", A ".cpp" would find the
"f" functions, but i guessed that it was unsafe
to change all the extensions to .cpp, thus 
implicitly declaring the project as a C++ project.

"/TP" option (if i recall its name) didn't seem
to work. I'm afraid it's an issue about C99
compliance. I didn't investigate further, though.









-- 
View this message in context: http://www.nabble.com/Channels-tp21852607p21905042.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Pinball wrote:
> 
> 
> 
> michael.gogins wrote:
>> 
>> Csound can indeed currently be compiled with MSVC, CsoundAC cannot
>> (thanks 
>> to limitations on the MSVC implementation of the Standard C++ Library in 
>> dynamic libraries).
>> 
> 
> I wanted to try to build a project from scratch,
> the DLL only, adding the required *.c and *.h
> files, fixing what was missing (looking at the 
> makefile provided). I didn't want to use mingw
> or scons or whatever.
> 
> The compiler didn't seem to find the "f math"
> functions (powf and so on) when the sources
> extension was ".c", A ".cpp" would find the
> "f" functions, but i guessed that it was unsafe
> to change all the extensions to .cpp, thus 
> implicitly declaring the project as a C++ project.
> 
> "/TP" option (if i recall its name) didn't seem
> to work. I'm afraid it's an issue about C99
> compliance. I didn't investigate further, though.
> 
> 

By the way... the "long long" type was also
an issue.



-- 
View this message in context: http://www.nabble.com/Channels-tp21852607p21905057.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net