sndobj-devel — SndObj Developer's List

Re: [Sndobj-devel] PySndObj, Python 2.4, Mac OS10.4

[Craig L. <lew...@mi...>]

I *finally* was able to get sndobj.py successfully generated and
installed on OSX (10.4.8), with Python 2.4.4

my initial problem was that I was continually getting this error when
I would try to 'import sndobj' from the python interpreter:

Traceback (most recent call last):
 File "<stdin>", line 1, in ?
 File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/sndobj.py",
line 4, in ?
   import _sndobj
ImportError: Failure linking new module:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/_sndobj.so:
Library not loaded: lib/libsndobj.dylib
 Referenced from:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/_sndobj.so
 Reason: image not found


the default Python that comes with OSX, on my machine, was Python
2.3.5.  however, i was running Python 2.4.4 from a different location.
 i needed this because of other  modules i am using with my
application.  it turned out, that in the SConstruct file, the variable
pythonpath needed to be changed from:

pythonpath = '/System/Library/Frameworks/Python.framework'
(the location of the original Python 2.3.5 install), to:

pythonpath = '/Library/Frameworks/Python.framework'
(the location of Python 2.4.4.)

however, once i did this, i was still having problems when i'd run
scons.  the build would complete, but no sndobj.py file could be
found.  so, after reading a little bit, i ran scons again with the
cache disabled:

%scons --cache-disable
(scons user guide here: http://www.scons.org/doc/HTML/scons-user.html)

when i did that, it completely rebuilt SndObj, including generating
the sndobj.py file, along with its libraries.

still, the problem was that the PySndObj files (sndobj.py, _sndobj.so,
libsndobj.dylib) were not being installed into my Python 2.4.4
framework automatically with the scons build.  instead, they were just
showing up in the install folder on my desktop, so i had to manually
install them into my Python framework.  from the SConstruct file, as
far as i can tell, it doesn't look like it's built to install the
PySndObj files.  is this correct?

either way, it's working now.

another issue i notice: in the SConstruct file, in the general
configuration section, the indenting seemed to be very complicated.
is there a reason for this?  i know that indenting is crucial to
proper python execution, and the mixed spaces and tabs in that section
really confused.  one of the reason i bring this up is because even
though i had set pythonpath in the code, when i ran:

%scons -h

i got a printout with an 'actual' value of pythonpath to be blank.
so, i had to manually set python by running

%scons pythonpath=/Library/Frameworks/Python.framework

of course, i was running scons so many times that maybe this is some
error on my part.  either way, i wanted to see if anyone else had
notice the indenting in that section, and could possibly explain it.

all that said, i'm curious to know what other people on this list are
using SndObj for in their Python applications.  my current application
is a Tkinter-based GUI that takes incoming signals from a USB
prototype keyboard and turns those into sound.  it's basically a MIDI
controller, without the MIDI.

ok.  thanks for getting back to me.

-craig


On 1/23/07, akonsu <ak...@gm...> wrote:
> Hello,
>
> you can build it from source for your version. it looks like you are
> on osx, so it should work. it worked for me on openbsd, osx is even
> easier.
>
> konstantin
>
> 2007/1/23, sonify <so...@av...>:
> > Hi Craig,
> > What architecture/ operating system?
> >
> >
> > On 23/01/2007, at 10:39 AM, Craig Lewiston wrote:
> >
> > > I've been having trouble getting SndObj to work in Python, before I
> > > finally realized that the current release is only built for Python
> > > 2.3.  I changed my PATH to point to the Apple's default Python install
> > > (2.3.5), and SndObj worked great within Python.  The problem is, my
> > > current application that I'm trying to add sound to uses other
> > > external modules that are only compatible with at least Python 2.4.
> > >
> > > Is there a way I can build SndObj for Python 2.4?  Do you only have to
> > > alter _sndobj.so to link to Python 2.4 on the system, or is there
> > > something more fundamental that needs to be done?
> > >
> > > thanks,
> > > craig
> > >
> > > ----------------------------------------------------------------------
> > > ---
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to
> > > share your
> > > opinions on IT & business topics through brief surveys - and earn cash
> > > http://www.techsay.com/default.php?
> > > page=join.php&p=sourceforge&CID=DEVDEV
> > > _______________________________________________
> > > Sndobj-devel mailing list
> > > Snd...@li...
> > > https://lists.sourceforge.net/lists/listinfo/sndobj-devel
> > >
> >
> > _________________________________________________
> > experimental polymedia: www.avatar.com.au
> > Sonic Communications Research Group,
> > University of Canberra:  www.canberra.edu.au/vc-forum/scrg
> > vip=Verbal Interactivity Project
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Sndobj-devel mailing list
> > Snd...@li...
> > https://lists.sourceforge.net/lists/listinfo/sndobj-devel
> >
>

Re: [Sndobj-devel] SndCoreAudio fixes

[sonify <so...@av...>]

Hi Victor,
I get a build error on intel OSX 10.4.8:

> g++ -O3 -fPIC -DWORDS_LITTLEENDIAN -DMACOSX -DJACK -Iinclude - 
> Iinclude/rfftw -I/system/library/Frameworks/CoreAudio.framework/ 
> Headers -c -o src/SndCoreAudio.os src/SndCoreAudio.cpp
> src/SndCoreAudio.cpp:225: error: expected unqualified-id before  
> '<<' token
> src/SndCoreAudio.cpp:256: error: expected unqualified-id before  
> '==' token
> scons: *** [src/SndCoreAudio.os] Error 1
> scons: building terminated because of errors.

May I suggest a little addition to the SConstruct script to alert  
people to which version of python is being used.

Before the line:

		if not msvctools:
(at about line 180)
insert
		print "python version:", getVersion()

BTW I'm building under python 2.4 OK.   I'll post on this further if  
there's a need.

David

On 25/01/2007, at 3:28 AM, Victor Lazzarini wrote:

> Dear all,
>
> I have committed to CVS some fixes to SndCoreAudio to handle non- 
> interleaved
> audio. I am wondering whether that was the problem with Intel
> hardware. If the audio device required non-interleaved audio, it  
> would not have
> worked. Would anyone care to test it?
>
> On the other hand the problem might be somewhere else...
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au/vc-forum/scrg
vip=Verbal Interactivity Project

[Sndobj-devel] SndCoreAudio fixes

[Victor L. <Vic...@nu...>]

Dear all,

I have committed to CVS some fixes to SndCoreAudio to handle non-interleaved
audio. I am wondering whether that was the problem with Intel
hardware. If the audio device required non-interleaved audio, it would not have
worked. Would anyone care to test it?

On the other hand the problem might be somewhere else...

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

[Sndobj-devel] manual in CVS

[Victor L. <Vic...@nu...>]

Dear all,

I have imported the manual into CVS, into a new module called
'manual'.

I have looked into moving to OpenOffice.org, but did not find it
easy. For the moment, I'll keep maintaining the manual as MS-Word
and releasing it as CVS.

The old html manual (out of date) is in the subdir html. If some work
is to be done with html, that can be a starting point perhaps.

Victor

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

Re: [Sndobj-devel] PySndObj, Python 2.4, Mac OS10.4

[akonsu <ak...@gm...>]

Hello,

you can build it from source for your version. it looks like you are
on osx, so it should work. it worked for me on openbsd, osx is even
easier.

konstantin

2007/1/23, sonify <so...@av...>:
> Hi Craig,
> What architecture/ operating system?
>
>
> On 23/01/2007, at 10:39 AM, Craig Lewiston wrote:
>
> > I've been having trouble getting SndObj to work in Python, before I
> > finally realized that the current release is only built for Python
> > 2.3.  I changed my PATH to point to the Apple's default Python install
> > (2.3.5), and SndObj worked great within Python.  The problem is, my
> > current application that I'm trying to add sound to uses other
> > external modules that are only compatible with at least Python 2.4.
> >
> > Is there a way I can build SndObj for Python 2.4?  Do you only have to
> > alter _sndobj.so to link to Python 2.4 on the system, or is there
> > something more fundamental that needs to be done?
> >
> > thanks,
> > craig
> >
> > ----------------------------------------------------------------------
> > ---
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to
> > share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?
> > page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Sndobj-devel mailing list
> > Snd...@li...
> > https://lists.sourceforge.net/lists/listinfo/sndobj-devel
> >
>
> _________________________________________________
> experimental polymedia: www.avatar.com.au
> Sonic Communications Research Group,
> University of Canberra:  www.canberra.edu.au/vc-forum/scrg
> vip=Verbal Interactivity Project
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>

Re: [Sndobj-devel] PySndObj, Python 2.4, Mac OS10.4

[sonify <so...@av...>]

Hi Craig,
What architecture/ operating system?


On 23/01/2007, at 10:39 AM, Craig Lewiston wrote:

> I've been having trouble getting SndObj to work in Python, before I
> finally realized that the current release is only built for Python
> 2.3.  I changed my PATH to point to the Apple's default Python install
> (2.3.5), and SndObj worked great within Python.  The problem is, my
> current application that I'm trying to add sound to uses other
> external modules that are only compatible with at least Python 2.4.
>
> Is there a way I can build SndObj for Python 2.4?  Do you only have to
> alter _sndobj.so to link to Python 2.4 on the system, or is there
> something more fundamental that needs to be done?
>
> thanks,
> craig
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au/vc-forum/scrg
vip=Verbal Interactivity Project

[Sndobj-devel] PySndObj, Python 2.4, Mac OS10.4

[Craig L. <lew...@mi...>]

I've been having trouble getting SndObj to work in Python, before I
finally realized that the current release is only built for Python
2.3.  I changed my PATH to point to the Apple's default Python install
(2.3.5), and SndObj worked great within Python.  The problem is, my
current application that I'm trying to add sound to uses other
external modules that are only compatible with at least Python 2.4.

Is there a way I can build SndObj for Python 2.4?  Do you only have to
alter _sndobj.so to link to Python 2.4 on the system, or is there
something more fundamental that needs to be done?

thanks,
craig

Re: [Sndobj-devel] sndobj/PySndObj manuals

[Victor L. <Vic...@nu...>]

The original SINUSEX  format is described in 
http://music.nuim.ie/vlazzarini/papers/09.pdf.
The implementation in the library is only half done; I got caught with
other things and never managed to finish it. I need to write
a reader for it and more testing needs to be done. Perhaps you might
want to wait until I am done with it?

Victor

At 17:00 22/01/2007, todd ingalls wrote:
>victor,
>do you have any reference to what the SINUSEX format is suppose to
>be? I was just wondering because I wanted to try to get that working.
>thanks.
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Sndobj-devel mailing list
>Snd...@li...
>https://lists.sourceforge.net/lists/listinfo/sndobj-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

Re: [Sndobj-devel] sndobj/PySndObj manuals

[todd i. <tes...@as...>]

victor,
do you have any reference to what the SINUSEX format is suppose to  
be? I was just wondering because I wanted to try to get that working.  
thanks. 

Re: [Sndobj-devel] sndobj/PySndObj manuals

[Victor L. <Vic...@nu...>]

Well, code changes, but compatibility has been so far
maintained and I feel this is the way to do things.

I think doing a html manual could be a good thing, but
I'd like to maintain a way of making PDFs with table of
contents for printing, to which pages can be added easily.
The MS Word version of the manual has worked for me
quite well in that respect. I might investigate moving it
to open office so we have a Free software base for
everything.

But that does not stop the manual being made html; the
only thing is that we would have to synchronise the
updates.

The way Csound5 has worked in the past ears is to use
XML and docbook to make the manual. But I'm really no keen
on writing XML, which I find a pain. However, if this is
found to be the best way, I can go with it. I'll have to learn
a little more about it though.

Victor


t 06:06 21/01/2007, you wrote:
>If code is changing, issues of  application/code version
>compatibilities need to be addresed up front.
>
>Perhaps a brief discussion might be appropriate before making a
>decision.
>
>My own preference is to have the manual distributed w. the code.
>That encourages keeping documentation to be kept up-to-date as
>changes to the code occur.
>Also fits into sourceforge/CSV structure seamlessly.
>
>_PDF's_ print well but do not encourage modularisation and hot-linking.
>Ditto _msword _(.doc) but they are not as big and are easier to edit.
>
>_HTML_ can be a pain to edit but templating can encourage consistency
>for a better look and feel.
>Apart from the (currently excellent) introductory material, there
>seems to be no one appropriate linear
>presentation of the material. What is important is that related stuff
>can be found. This to me means hyperlinks.
>Not that it's the be-all and end-all, but the (online) documentation
>for python works well IMO and we could do worse.
>
>An HTML manual can more easily be browsed on-line and I would have
>thought  that would encourage new users.
>
>_OpenOffice_ functions (in this context) like msword. It can open ms
>word docos but not sure about the
>other way around. Can save to PDF and HTML. HTML tools look better
>than msword. Is is not as widely used as msword.
>
>I've no desire  to reinvent the wheel, Victor. Perhaps we could
>experiment with some samples that export
>to html? Seems simple, but would depend on how "fancy" you want it.
>My preference is for simplicity,
>clarity, ease of use over "bells and whistles".
>
>Thoughts? I'd be happier if we did some experiments before committing
>to any one solution, unless you think it's clear.
>I'm not in a busting hurry, so if you want to make your updates
>first, that's cool. I just ned to " put it on the scheduler stack" :-)
>
>David
>
>
>On 20/01/2007, at 8:37 PM, Victor Lazzarini wrote:
>
> > I'll try and import the manual sources (they are
> > all MS-Word docs) and then you can work on them,
> > if you'd like.
> >
> > The manual used to be html, but then I moved it to
> > MS-Word because I found it easier to maintain and to
> > create PDFs.
> >
> > Please post the e-mail re importing modules.
> >
> > all the best
> >
> > Victor
> >
> >>
> >> It is interesting to note the current discussion about
> >> manual and   versions and dates on CS-dev.
> >>
> >> A 'wild' discussion about manuals and documentation is
> >> also currently   occurring on supercollider-dev.
> >> Must be something in the water. :-)
> >>
> >> May I suggest an on-line (html) manual for sndobj ....
> >> and a   separate one for PySndObj ?
> >>
> >> I'd be happy to work, over time, on the latter. It's
> >> currently   exellent if you know what you're doing,
> >> however I do think it could be made a bit less daunting
> >> for those less   experienced.
> >>
> >> Victor, re the correspondence  we had about python's from
> >> "import x"   c f "from x import *", I've had some
> >> correspondence with the mac-  python SIG 's Piet Oussoren
> >> (well known in those parts)  and he has   provided a
> >> detailed discussion. I'll post/email it if anyone's
> >> interested.
> >>
> >> ciau,
> >>
> >> Davud
> >> _________________________________________________
> >> experimental polymedia:    www.avatar.com.au
> >> Sonic Communications Research Group,
> >> University of Canberra:
> >> www.canberra.edu.au/vc-forum/scrg vip=Verbal Interactivity
> >> Project
> >>
> >>
> >>
> >>
> >> ----------------------------------------------------------
> >> --------------- Take Surveys. Earn Cash. Influence the
> >> Future of IT Join SourceForge.net's Techsay panel and
> >> you'll get the chance to share your opinions on IT &
> >> business topics through brief surveys - and earn cash
> >>
> > http://www.techsay.com/default.php?
> > page=join.php&p=sourceforge&CID=DEVDEV
> >> _______________________________________________
> >> Sndobj-devel mailing list
> >> Snd...@li...
> >> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
> >
> > ----------------------------------------------------------------------
> > ---
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to
> > share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?
> > page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Sndobj-devel mailing list
> > Snd...@li...
> > https://lists.sourceforge.net/lists/listinfo/sndobj-devel
> >
>
>_________________________________________________
>experimental polymedia: www.avatar.com.au
>Sonic Communications Research Group,
>University of Canberra: www.canberra.edu.au/vc-forum/scrg
>vip=Verbal Interactivity Project
>
>
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Sndobj-devel mailing list
>Snd...@li...
>https://lists.sourceforge.net/lists/listinfo/sndobj-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

Re: [Sndobj-devel] sndobj/PySndObj manuals

[sonify <so...@av...>]

If code is changing, issues of  application/code version  
compatibilities need to be addresed up front.

Perhaps a brief discussion might be appropriate before making a  
decision.

My own preference is to have the manual distributed w. the code.
That encourages keeping documentation to be kept up-to-date as  
changes to the code occur.
Also fits into sourceforge/CSV structure seamlessly.

_PDF's_ print well but do not encourage modularisation and hot-linking.
Ditto _msword _(.doc) but they are not as big and are easier to edit.

_HTML_ can be a pain to edit but templating can encourage consistency  
for a better look and feel.
Apart from the (currently excellent) introductory material, there  
seems to be no one appropriate linear
presentation of the material. What is important is that related stuff  
can be found. This to me means hyperlinks.
Not that it's the be-all and end-all, but the (online) documentation  
for python works well IMO and we could do worse.

An HTML manual can more easily be browsed on-line and I would have  
thought  that would encourage new users.

_OpenOffice_ functions (in this context) like msword. It can open ms  
word docos but not sure about the
other way around. Can save to PDF and HTML. HTML tools look better  
than msword. Is is not as widely used as msword.

I've no desire  to reinvent the wheel, Victor. Perhaps we could  
experiment with some samples that export
to html? Seems simple, but would depend on how "fancy" you want it.  
My preference is for simplicity,
clarity, ease of use over "bells and whistles".

Thoughts? I'd be happier if we did some experiments before committing  
to any one solution, unless you think it's clear.
I'm not in a busting hurry, so if you want to make your updates  
first, that's cool. I just ned to " put it on the scheduler stack" :-)

David


On 20/01/2007, at 8:37 PM, Victor Lazzarini wrote:

> I'll try and import the manual sources (they are
> all MS-Word docs) and then you can work on them,
> if you'd like.
>
> The manual used to be html, but then I moved it to
> MS-Word because I found it easier to maintain and to
> create PDFs.
>
> Please post the e-mail re importing modules.
>
> all the best
>
> Victor
>
>>
>> It is interesting to note the current discussion about
>> manual and   versions and dates on CS-dev.
>>
>> A 'wild' discussion about manuals and documentation is
>> also currently   occurring on supercollider-dev.
>> Must be something in the water. :-)
>>
>> May I suggest an on-line (html) manual for sndobj ....
>> and a   separate one for PySndObj ?
>>
>> I'd be happy to work, over time, on the latter. It's
>> currently   exellent if you know what you're doing,
>> however I do think it could be made a bit less daunting
>> for those less   experienced.
>>
>> Victor, re the correspondence  we had about python's from
>> "import x"   c f "from x import *", I've had some
>> correspondence with the mac-  python SIG 's Piet Oussoren
>> (well known in those parts)  and he has   provided a
>> detailed discussion. I'll post/email it if anyone's
>> interested.
>>
>> ciau,
>>
>> Davud
>> _________________________________________________
>> experimental polymedia:    www.avatar.com.au
>> Sonic Communications Research Group,
>> University of Canberra:
>> www.canberra.edu.au/vc-forum/scrg vip=Verbal Interactivity
>> Project
>>
>>
>>
>>
>> ----------------------------------------------------------
>> --------------- Take Surveys. Earn Cash. Influence the
>> Future of IT Join SourceForge.net's Techsay panel and
>> you'll get the chance to share your opinions on IT &
>> business topics through brief surveys - and earn cash
>>
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Sndobj-devel mailing list
>> Snd...@li...
>> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au/vc-forum/scrg
vip=Verbal Interactivity Project





_____________________________
David Worrall: so...@av...

[Sndobj-devel] Fwd: importing namespaces/modules 1of3

[sonify <so...@av...>]

Begin forwarded message:

> From: Piet van Oostrum <pi...@cs...>
> Date: 19 January 2007 8:27:39 PM
> To: David Worrall <vi...@av...>
> Cc: Pyt...@py...
> Subject: Re: [Pythonmac-SIG] importing namespaces/modules
>
>>>>>> David Worrall <vi...@av...> (DW) wrote:
>
>> DW> Hello all,
>> DW> I've got a query which is probably obvious for people more
>> DW> experienced than I
>> DW> but I can't find any exact reference to it elsewhere.
>> DW> It's not mac specific, but hey, I already belong to too many dev
>> DW> groups...   :-)
>> DW> The discussion at http://docs.python.org/tut/node11.html is OK  
>> but it
>> DW> doesn't really answer my query.
>
>> DW> I note that increasingly programmers are deprecating
>
>>>>>> from module import *
>
>> DW>   in favour of
>>>>>> import module
>
>> DW> which is fair enough, as explicit attributes make code more  
>> readable.
>
>> DW> Are the functions/classes/whatevers that are imported into the
>> DW> namespace with >>> import module
>> DW> but not otherwise referenced, explicitly loaded into the python
>> DW> "workspace" (excuse me, I'm an unrepentant APL programmer)
>> DW> including the __doc__ strings etc etc or not?
>
> The whole module is always loaded into memory, no matter what  
> format of
> the import statement you use.
>
>> DW> And if so, do they remain in the .pyc image?
>
> Every module has its own .pyc file. The .pyc file of the importing  
> module
> only contains the bytecode for the import statement, not the  
> bytecode of
> the imported module, because that is in thye .pyc file of the imported
> module.
>
>> DW> And after py2app?
>
> I am not very familiar with py2app, but I think it packs up the  
> necessary
> .pyc modules into the executable. But I am quite sure it will  
> always pack
> the whole .pyc file. It would be unfeasible to extract only a part  
> of a
> .pyc file as there will be all kinds of internal references in the  
> module.
> Some of the dependencies might be so dynamic that a static analyses  
> would
> be unable to detect them.
>
>> DW> In the case where module is quite large (think wx or twisted  
>> for eg)
>> DW> I'm wondering what are the relative advantages/disadvantages  
>> of, for
>> DW> example
>>>>>> import twisted
>>>>>> class MessageHandler(twisted.internet.protocol.DatagramProtocol):
>
>> DW> compared with
>>>>>> from twisted.internet.protocol import DatagramProtocol
>> DW> Class MessageHandler(DatagramProtocol):
>
>> DW> other than the obvious easy of reading
>> DW> "twisted.internet.protocol.DatagramProtocol" in a large  
>> environment
>> DW> with many imported modules, which is my situation.
>
> The advantages have nothing to do with size. In the above example  
> it is
> mainly readability, and maybe name clashes with a DatagramProtocol  
> from
> another module. The main reason for
> deprecating from module import * is the pollution of your  
> namespace. E.g.
>
> ERRORCODE = -1
> SUCCESSCODE = 1
>
> from module import *
>
> Now suppose this code has been running correctly for a while. Then a
> revision is made in module which adds the variable ERRORCODE to  
> module.py
> with a different value. Now suddenly the value of ERRORCODE is  
> different in
> your program which may lead to subtle bugs.
>
> You may think this can be avoided by putting all import statements  
> first in
> your program before defining any variables (or classes, functions,  
> etc).
> But then you can have the same interaction between the different  
> modules.
>
> from graphics import *
> from statistics import *
>
> Now statistics can `shadow' a variable from graphics, for example  
> if the
> both have a function 'draw'.
> Of course the same could happen if you write:
>
> from graphics import paint, draw
> from statistics import draw, average
>
> but at least then it is visible in your code.
>
> And the most secure would be to use import graphics, and then use
> graphics.draw etc.
> -- 
> Piet van Oostrum <pi...@cs...>
> URL: http://www.cs.uu.nl/~piet [PGP 8DAE142BE17999C4]
> Private email: pi...@va...
>

_____________________________
David Worrall: so...@av...

[Sndobj-devel] Fwd: importing namespaces/modules 3of3

[sonify <so...@av...>]

Begin forwarded message:

> From: Ronald Oussoren <ron...@ma...>
> Date: 20 January 2007 12:08:36 AM
> To: Piet van Oostrum <pi...@cs...>
> Cc: David Worrall <vi...@av...>, Pyt...@py...
> Subject: Re: [Pythonmac-SIG] importing namespaces/modules
>
>
> On Friday, January 19, 2007, at 01:45PM, "Piet van Oostrum"  
> <pi...@cs...> wrote:
>>
>>> DW> And after py2app?
>>
>> I am not very familiar with py2app, but I think it packs up the  
>> necessary
>> .pyc modules into the executable. But I am quite sure it will  
>> always pack
>> the whole .pyc file. It would be unfeasible to extract only a part  
>> of a
>> .pyc file as there will be all kinds of internal references in the  
>> module.
>> Some of the dependencies might be so dynamic that a static  
>> analyses would
>> be unable to detect them.
>
> py2app always includes entire pyc files and looks at import  
> statements to detect dependencies.
>
> Ronald
>

_____________________________
David Worrall: so...@av...

[Sndobj-devel] Fwd: importing namespaces/modules 2of3

[sonify <so...@av...>]

Begin forwarded message:

> From: Piet van Oostrum <pi...@cs...>
> Date: 19 January 2007 8:37:00 PM
> To: David Worrall <vi...@av...>
> Cc: Pyt...@py...
> Subject: Re: [Pythonmac-SIG] importing namespaces/modules
>
> I should add another difference in the behaviour of variables  
> import in one
> or the other way. This can lead to subtle differences.
>
> If you use 'from module import x, y' (or 'from module import *')  
> Python
> makes new `bindings' of the names `x' and `y' in the importing  
> module with
> the values these names had in the imported module. However they are
> independent of the original ones. So if you execute an assignment  
> to x in
> the original module, e.g. in a function that was defined there and  
> that you
> also imported, the change in x is not reflected in the imported x,  
> and vice
> versa. This can lead to unexpected behaviour.
>
> If, however, you say 'import module' and then use module.x, then it  
> is the
> same variable, and changes in the imported module's x will be  
> visible in
> the importing module's module.x and vice versa.
>
> -- 
> Piet van Oostrum <pi...@cs...>
> URL: http://www.cs.uu.nl/~piet [PGP 8DAE142BE17999C4]
> Private email: pi...@va...
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au/vc-forum/scrg
vip=Verbal Interactivity Project





experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au

Re: [Sndobj-devel] sndobj/PySndObj manuals

[David W. <vi...@av...>]

If code is changing, issues of  application/code version  
compatibilities need to be addresed up front.

Perhaps a brief discussion might be appropriate before making a  
decision.

My own preference is to have the manual distributed w. the code.
That encourages keeping documentation to be kept up-to-date as  
changes to the code occur.
Also fits into sourceforge/CSV structure seamlessly.

_PDF's_ print well but do not encourage modularisation and hot-linking.
Ditto _msword _(.doc) but they are not as big and are easier to edit.

_HTML_ can be a pain to edit but templating can encourage consistency  
for a better look and feel.
Apart from the (currently excellent) introductory material, there  
seems to be no one appropriate linear
presentation of the material. What is important is that related stuff  
can be found. This to me means hyperlinks.
Not that it's the be-all and end-all, but the (online) documentation  
for python works well IMO and we could do worse.

An HTML manual can more easily be browsed on-line and I would have  
thought  that would encourage new users.

_OpenOffice_ functions (in this context) like msword. It can open ms  
word docos but not sure about the
other way around. Can save to PDF and HTML. HTML tools look better  
than msword. Is is not as widely used as msword.

I've no desire  to reinvent the wheel, Victor. Perhaps we could  
experiment with some samples that export
to html? Seems simple, but would depend on how "fancy" you want it.  
My preference is for simplicity,
clarity, ease of use over "bells and whistles".

Thoughts? I'd be happier if we did some experiments before committing  
to any one solution, unless you think it's clear.
I'm not in a busting hurry, so if you want to make your updates  
first, that's cool. I just ned to " put it on the scheduler stack" :-)

David


On 20/01/2007, at 8:37 PM, Victor Lazzarini wrote:

> I'll try and import the manual sources (they are
> all MS-Word docs) and then you can work on them,
> if you'd like.
>
> The manual used to be html, but then I moved it to
> MS-Word because I found it easier to maintain and to
> create PDFs.
>
> Please post the e-mail re importing modules.
>
> all the best
>
> Victor
>
>>
>> It is interesting to note the current discussion about
>> manual and   versions and dates on CS-dev.
>>
>> A 'wild' discussion about manuals and documentation is
>> also currently   occurring on supercollider-dev.
>> Must be something in the water. :-)
>>
>> May I suggest an on-line (html) manual for sndobj ....
>> and a   separate one for PySndObj ?
>>
>> I'd be happy to work, over time, on the latter. It's
>> currently   exellent if you know what you're doing,
>> however I do think it could be made a bit less daunting
>> for those less   experienced.
>>
>> Victor, re the correspondence  we had about python's from
>> "import x"   c f "from x import *", I've had some
>> correspondence with the mac-  python SIG 's Piet Oussoren
>> (well known in those parts)  and he has   provided a
>> detailed discussion. I'll post/email it if anyone's
>> interested.
>>
>> ciau,
>>
>> Davud
>> _________________________________________________
>> experimental polymedia:    www.avatar.com.au
>> Sonic Communications Research Group,
>> University of Canberra:
>> www.canberra.edu.au/vc-forum/scrg vip=Verbal Interactivity
>> Project
>>
>>
>>
>>
>> ----------------------------------------------------------
>> --------------- Take Surveys. Earn Cash. Influence the
>> Future of IT Join SourceForge.net's Techsay panel and
>> you'll get the chance to share your opinions on IT &
>> business topics through brief surveys - and earn cash
>>
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Sndobj-devel mailing list
>> Snd...@li...
>> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au/vc-forum/scrg
vip=Verbal Interactivity Project

Re: [Sndobj-devel] sndobj/PySndObj manuals

[Victor L. <vic...@nu...>]

I'll try and import the manual sources (they are
all MS-Word docs) and then you can work on them,
if you'd like.

The manual used to be html, but then I moved it to
MS-Word because I found it easier to maintain and to
create PDFs.

Please post the e-mail re importing modules.

all the best

Victor

>
> It is interesting to note the current discussion about
> manual and   versions and dates on CS-dev.
>
> A 'wild' discussion about manuals and documentation is
> also currently   occurring on supercollider-dev.
> Must be something in the water. :-)
>
> May I suggest an on-line (html) manual for sndobj ....
> and a   separate one for PySndObj ?
>
> I'd be happy to work, over time, on the latter. It's
> currently   exellent if you know what you're doing,
> however I do think it could be made a bit less daunting
> for those less   experienced.
>
> Victor, re the correspondence  we had about python's from
> "import x"   c f "from x import *", I've had some
> correspondence with the mac-  python SIG 's Piet Oussoren
> (well known in those parts)  and he has   provided a
> detailed discussion. I'll post/email it if anyone's
> interested.
>
> ciau,
>
> Davud
> _________________________________________________
> experimental polymedia:    www.avatar.com.au
> Sonic Communications Research Group,
> University of Canberra:
> www.canberra.edu.au/vc-forum/scrg vip=Verbal Interactivity
> Project
>
>
>
>
> ----------------------------------------------------------
> --------------- Take Surveys. Earn Cash. Influence the
> Future of IT Join SourceForge.net's Techsay panel and
> you'll get the chance to share your opinions on IT &
> business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel

Re: [Sndobj-devel] CFFI build errors

[Victor L. <vic...@nu...>]

What scons does is to find the Python version it runs on
and then attempt to build with it. If scons is running
under 2.4 it will be build for that. But, since on OSX
2.3 is what comes with the OS, there might be a path
problem. I think I have the Python framework set to be
in /System/Library/Frameworks. Is the 2.4 framework there?

Otherwise can you give me the location of Python.h and
the framework for 2.4. The paths in SConstruct need to
be edited probably.

In fact, if you know how to work with scons (it's Python
anyway...), you could be added as a developer, so that you
can
commit the fixes yourself.

Victor
>
> BTW,
> We had scons trouble building with python 2.4 under
> OSX10.3.9 on mac PPC It scons OK with python2.3
>
>   It builds ok, on intel mac OSX10.4.8under python2.4.3
>
> You probably know about this already, but at the mo, it
> _is_ a   dependency.
>
> - David
>
>
> On 20/01/2007, at 6:56 AM, Victor Lazzarini wrote:
>
> > Thanks, it builds now.
> >
> > I'll try and add the other dependencies for OSX, so
> > the module can be built from scons.
> >
> > Regards
> >
> > Victor
> >>
> >> i believe these are as a result of not having the
> macros >> SWIG   SWIGCFFI defined.
> >>
> >> in g++ i need -DSWIG -DSWIGCFFI
> >>
> >>
> >>
>
> _________________________________________________
> experimental polymedia:    www.avatar.com.au
> Sonic Communications Research Group,
> University of Canberra:
> www.canberra.edu.au/vc-forum/scrg vip=Verbal Interactivity
> Project
>
>
>

[Sndobj-devel] sndobj/PySndObj manuals

[David W. <vi...@av...>]

It is interesting to note the current discussion about manual and  
versions and dates on CS-dev.

A 'wild' discussion about manuals and documentation is also currently  
occurring on supercollider-dev.
Must be something in the water. :-)

May I suggest an on-line (html) manual for sndobj ....  and a  
separate one for PySndObj ?

I'd be happy to work, over time, on the latter. It's currently  
exellent if you know what you're doing, however
I do think it could be made a bit less daunting for those less  
experienced.

Victor, re the correspondence  we had about python's from "import x"  
c f "from x import *", I've had some correspondence with the mac- 
python SIG 's Piet Oussoren (well known in those parts)  and he has  
provided a detailed discussion. I'll post/email it if anyone's  
interested.

ciau,

Davud
_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 www.canberra.edu.au/vc-forum/scrg
vip=Verbal Interactivity Project

Re: [Sndobj-devel] CFFI build errors

[Victor L. <vic...@nu...>]

Thanks, it builds now.

I'll try and add the other dependencies for OSX, so
the module can be built from scons.

Regards

Victor
>
> i believe these are as a result of not having the macros
> SWIG   SWIGCFFI defined.
>
> in g++ i need -DSWIG -DSWIGCFFI
>
>
>
> On Jan 19, 2007, at 12:37 PM, Victor Lazzarini wrote:
>
> > Todd,
> >
> > here's the compilation errors (this is Windows and
> > I am using last night's CVS):
> >
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjEqualSndObj(SndObj*, SndObj*)':
> > cffi\AudioDefs_wrap.cc:308: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:308: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjSumSndObj(SndObj*, SndObj*)':
> > cffi\AudioDefs_wrap.cc:452: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:452: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjSubtractSndObj(SndObj*, SndObj*)':
> > cffi\AudioDefs_wrap.cc:470: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:470: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjMultiplySndObj(SndObj*, SndObj*)':
> > cffi\AudioDefs_wrap.cc:488: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:488: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjSumFloat(SndObj*, float)':
> > cffi\AudioDefs_wrap.cc:506: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:506: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjSubtractFloat(SndObj*, float)':
> > cffi\AudioDefs_wrap.cc:524: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:524: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > cffi\AudioDefs_wrap.cc: In function `SndObj*
> > _wrap_SndObj_SndObjMultiplyFloat(SndObj*, float)':
> > cffi\AudioDefs_wrap.cc:542: error: no matching function
> > for call to `SndObj::SndObj(SndObj)'
> > src/SndObj.h:244: note: candidates are:
> > SndObj::SndObj(SndObj&)
> > src/SndObj.h:241: note:
> > SndObj::SndObj(SndObj*, int, float)
> > cffi\AudioDefs_wrap.cc:542: error:   initializing
> > argument 1 of `SndObj SndObj::operator=(SndObj)'
> > scons: *** [cffi\AudioDefs_wrap.o] Error 1
> >
> > I hope this helps.
> >
> > Victpr
> >
> >
> ----------------------------------------------------------
> > ------------  ---
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the
> > chance to   share your
> > opinions on IT & business topics through brief surveys -
> > and earn cash http://www.techsay.com/default.php?
> > page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Sndobj-devel mailing list
> > Snd...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel
>
>
> ----------------------------------------------------------
> --------------- Take Surveys. Earn Cash. Influence the
> Future of IT Join SourceForge.net's Techsay panel and
> you'll get the chance to share your opinions on IT &
> business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel

Re: [Sndobj-devel] CFFI build errors

[todd i. <tes...@as...>]

i believe these are as a result of not having the macros SWIG  
SWIGCFFI defined.

in g++ i need -DSWIG -DSWIGCFFI



On Jan 19, 2007, at 12:37 PM, Victor Lazzarini wrote:

> Todd,
>
> here's the compilation errors (this is Windows and
> I am using last night's CVS):
>
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjEqualSndObj(SndObj*, SndObj*)':
> cffi\AudioDefs_wrap.cc:308: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:308: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjSumSndObj(SndObj*, SndObj*)':
> cffi\AudioDefs_wrap.cc:452: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:452: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjSubtractSndObj(SndObj*, SndObj*)':
> cffi\AudioDefs_wrap.cc:470: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:470: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjMultiplySndObj(SndObj*, SndObj*)':
> cffi\AudioDefs_wrap.cc:488: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:488: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjSumFloat(SndObj*, float)':
> cffi\AudioDefs_wrap.cc:506: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:506: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjSubtractFloat(SndObj*, float)':
> cffi\AudioDefs_wrap.cc:524: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:524: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> cffi\AudioDefs_wrap.cc: In function `SndObj*
> _wrap_SndObj_SndObjMultiplyFloat(SndObj*, float)':
> cffi\AudioDefs_wrap.cc:542: error: no matching function for
> call to `SndObj::SndObj(SndObj)'
> src/SndObj.h:244: note: candidates are:
> SndObj::SndObj(SndObj&)
> src/SndObj.h:241: note:
> SndObj::SndObj(SndObj*, int, float)
> cffi\AudioDefs_wrap.cc:542: error:   initializing argument 1
> of `SndObj SndObj::operator=(SndObj)'
> scons: *** [cffi\AudioDefs_wrap.o] Error 1
>
> I hope this helps.
>
> Victpr
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel

[Sndobj-devel] CFFI build errors

[Victor L. <vic...@nu...>]

Todd,

here's the compilation errors (this is Windows and
I am using last night's CVS):

cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjEqualSndObj(SndObj*, SndObj*)':
cffi\AudioDefs_wrap.cc:308: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:308: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjSumSndObj(SndObj*, SndObj*)':
cffi\AudioDefs_wrap.cc:452: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:452: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjSubtractSndObj(SndObj*, SndObj*)':
cffi\AudioDefs_wrap.cc:470: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:470: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjMultiplySndObj(SndObj*, SndObj*)':
cffi\AudioDefs_wrap.cc:488: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:488: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjSumFloat(SndObj*, float)':
cffi\AudioDefs_wrap.cc:506: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:506: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjSubtractFloat(SndObj*, float)':
cffi\AudioDefs_wrap.cc:524: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:524: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
cffi\AudioDefs_wrap.cc: In function `SndObj*
_wrap_SndObj_SndObjMultiplyFloat(SndObj*, float)':
cffi\AudioDefs_wrap.cc:542: error: no matching function for
call to `SndObj::SndObj(SndObj)'
src/SndObj.h:244: note: candidates are:
SndObj::SndObj(SndObj&)
src/SndObj.h:241: note:                
SndObj::SndObj(SndObj*, int, float)
cffi\AudioDefs_wrap.cc:542: error:   initializing argument 1
of `SndObj SndObj::operator=(SndObj)'
scons: *** [cffi\AudioDefs_wrap.o] Error 1

I hope this helps.

Victpr

Re: [Sndobj-devel] CFFI scons target

[todd i. <tes...@as...>]

PS. yes it does and this should probably be in a readme

on darwin, if the wrapper file is called sndobj_wrap.cpp it can be  
built with something like

g++ -dynamiclib  sndobj_wrap.cpp -DMACOSX -DSWIG -DSWIGCFFI -I/System/ 
Library/Fra
meworks/CoreAudio.framework/Headers -I../include -I./ -I../include/ 
SndObj ../lib
/libsndobj.a -framework CoreAudio -framework Carbon -framework  
CoreMIDI -framewo
rk OpenGL -framework AGL -framework IOKit -framework QuickTime - 
fpascal-strings
-o sndobj_wrap.dylib



On Jan 19, 2007, at 8:21 AM, Victor Lazzarini wrote:

> Hi all,
>
> I have added a CFFI module build option to scons (in CVS now),
>
> scons lispmodule=1
>
> will attempt to build the CFFI interface. However, I could not  
> build it,
> as the wrapper code generated by SWIG had some problems. I did not
> touch the interface file because I don't really know much about it,  
> but it
> needs fixing. The CFFI SConstruct target might have problems, but
> I can't test it since it fails at the wrapper compilation.
>
> One question is, does the module has any external dependencies  
> (headers,
> libs)?
>
> All the best
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel

Re: [Sndobj-devel] CFFI scons target

[todd i. <tes...@as...>]

victor - what problems did the wrapper code have? can you send the  
error outputs



On Jan 19, 2007, at 8:21 AM, Victor Lazzarini wrote:

> Hi all,
>
> I have added a CFFI module build option to scons (in CVS now),
>
> scons lispmodule=1
>
> will attempt to build the CFFI interface. However, I could not  
> build it,
> as the wrapper code generated by SWIG had some problems. I did not
> touch the interface file because I don't really know much about it,  
> but it
> needs fixing. The CFFI SConstruct target might have problems, but
> I can't test it since it fails at the wrapper compilation.
>
> One question is, does the module has any external dependencies  
> (headers,
> libs)?
>
> All the best
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sndobj-devel mailing list
> Snd...@li...
> https://lists.sourceforge.net/lists/listinfo/sndobj-devel

[Sndobj-devel] CFFI scons target

[Victor L. <Vic...@nu...>]

Hi all,

I have added a CFFI module build option to scons (in CVS now),

scons lispmodule=1

will attempt to build the CFFI interface. However, I could not build it,
as the wrapper code generated by SWIG had some problems. I did not
touch the interface file because I don't really know much about it, but it
needs fixing. The CFFI SConstruct target might have problems, but
I can't test it since it fails at the wrapper compilation.

One question is, does the module has any external dependencies (headers,
libs)?

All the best

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth