pyMsgCb.cpp and pyMsgCb_stub.cpp

[Felipe Sateler]

Why are this two versions needed? The second one is used for the Java module,
while the first is used for the rest of the wrappers. Why can't the Java
module use the same one? I'm trying to separate all modules, and this means
that all common code should go into a shared library. This, of course, should
include pyMsgCb.cpp


--
Felipe Sateler


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel

[Felipe Sateler]

Hello, anyone?

El 15/06/08 12:05 Felipe Sateler escribió:
> Why are this two versions needed? The second one is used for the Java
> module, while the first is used for the rest of the wrappers. Why can't the
> Java module use the same one? I'm trying to separate all modules, and this
> means that all common code should go into a shared library. This, of
> course, should include pyMsgCb.cpp



--
Saludos,
Felipe Sateler


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel

[Michael Gogins]

There are good reasons why the different wrapper module filenames cannot be the same (indeed, they used to be the same, but it didn't work).

1. Both Python and Lua have strict naming requirements for wrapper modules -- but the naming requirements are not the same;
   therefore, the Python and Lua wrappers simply can't go into the same file.

2. Some people want wrappers for one language, other people want wrappers for another language.
   Under these circumstances, it is easier to maintain the build by separating the modules.

3. In some of the builds (e.g. Microsoft Visual Studio) code using the standard C++ library cannot be exported;
   in those builds, libraries using the standard C++ library must be static libraries (e.g. csnd, CsoundAC).

4. So, I have factored out the build into the following logical layers:

   +---------------------+--------------------+-------------------+
   | SWIG Python module  |  SWIG Java module  |  SWIG Lua module  |
   +---------------------+--------------------+-------------------+
   | csnd library (static in some builds, shared in other builds) |
   +--------------------------------------------------------------+
   |                    Csound API shared library                 |
   +--------------------------------------------------------------+

Hope this helps,

Mike


   

-----Original Message-----

>From: Felipe Sateler <fsateler@...>
>Sent: Jun 15, 2008 12:05 PM
>To: Developer discussions <csound-devel@...>
>Subject: Re: [Cs-dev] pyMsgCb.cpp and pyMsgCb_stub.cpp
>
>Hello, anyone?
>
>El 15/06/08 12:05 Felipe Sateler escribió:
>> Why are this two versions needed? The second one is used for the Java
>> module, while the first is used for the rest of the wrappers. Why can't the
>> Java module use the same one? I'm trying to separate all modules, and this
>> means that all common code should go into a shared library. This, of
>> course, should include pyMsgCb.cpp
>
>
>
>--
>Saludos,
>Felipe Sateler

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel

[Felipe Sateler]

I understand that (and in fact I have been working on further separating the
modules each into it's own library). What I don't is why the pyMsgCb isn't
part of the csnd library, and why the java module uses a different
implementation.

El 15/06/08 12:41 Michael Gogins escribió:

> There are good reasons why the different wrapper module filenames cannot be
> the same (indeed, they used to be the same, but it didn't work).
>
> 1. Both Python and Lua have strict naming requirements for wrapper modules
> -- but the naming requirements are not the same; therefore, the Python and
> Lua wrappers simply can't go into the same file.
>
> 2. Some people want wrappers for one language, other people want wrappers
> for another language. Under these circumstances, it is easier to maintain
> the build by separating the modules.
>
> 3. In some of the builds (e.g. Microsoft Visual Studio) code using the
> standard C++ library cannot be exported; in those builds, libraries using
> the standard C++ library must be static libraries (e.g. csnd, CsoundAC).
>
> 4. So, I have factored out the build into the following logical layers:
>
>    +---------------------+--------------------+-------------------+
>
>    | SWIG Python module  |  SWIG Java module  |  SWIG Lua module  |
>
>    +---------------------+--------------------+-------------------+
>
>    | csnd library (static in some builds, shared in other builds) |
>
>    +--------------------------------------------------------------+
>
>    |                    Csound API shared library                 |
>
>    +--------------------------------------------------------------+
>
> Hope this helps,
>
> Mike
>
>
>
>
> -----Original Message-----
>
> >From: Felipe Sateler <fsateler@...>
> >Sent: Jun 15, 2008 12:05 PM
> >To: Developer discussions <csound-devel@...>
> >Subject: Re: [Cs-dev] pyMsgCb.cpp and pyMsgCb_stub.cpp
> >
> >Hello, anyone?
> >
> >El 15/06/08 12:05 Felipe Sateler escribió:
> >> Why are this two versions needed? The second one is used for the Java
> >> module, while the first is used for the rest of the wrappers. Why can't
> >> the Java module use the same one? I'm trying to separate all modules,
> >> and this means that all common code should go into a shared library.
> >> This, of course, should include pyMsgCb.cpp
> >
> >--
> >Saludos,
> >Felipe Sateler
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@...
> https://lists.sourceforge.net/lists/listinfo/csound-devel

--
Saludos,
Felipe Sateler


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel

[Michael Gogins]

I believe the callback stuff has hand-written wrapper code that has
to be different for different languages.

Regards,
Mike

----- Original Message -----
From: "Felipe Sateler" <fsateler@...>
To: "Developer discussions" <csound-devel@...>
Sent: Sunday, June 15, 2008 12:51 PM
Subject: Re: [Cs-dev] pyMsgCb.cpp and pyMsgCb_stub.cpp


> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php


--------------------------------------------------------------------------------


> _______________________________________________
> Csound-devel mailing list
> Csound-devel@...
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel