I don't think most developers are going to be put off by finding this kind
of mild disorganization. If it's important to you, perhaps you could get
one of your students to become a Csound developer and factor out the
sources into one opcode per .c file.

Original Message:
-----------------
From: Richard Boulanger rboulanger@berklee.edu
Date: Fri, 11 Feb 2005 12:03:28 -0500
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] Question About the Organization of the Csound Sources


I understand what you are saying.  That's cool and thanks for the tip.

It worked here on my Mac in the Terminal.  Cool.  (I need to learn grep for
sure.)

BUT...

Doesn't it make sense, that in this wonderful effort to cleanup, organize,
etc. that you might help future developers and especially students/teachers,
to not require them to hunt for everything? Why not "standardize" the
sources and just reveal what is "in" Csound.

Or

Why not just put everything in opcodes.c and opcodes.h?

Why are some here and some there? And why are some separate and some grouped
into groups that have no logical affiliation?

Isn't this one of the very things that ALWAYS frustrated new developers
about Csound - that it took them a few hours/days to figure out what was
there and how things were "organized." (if at all).

Rick

 2/11/05 11:48 AM, gogins@pipeline.com at gogins@pipeline.com wrote:

> I will always prefer to fix bugs or add new functionality, over fixing
what
> is not broken.
> 
> Anyone who wants to find anything in Csound 5 only has to go to the
csound5
> directory and:
> 
> grep findthis */*.c
> 
> Original Message:
> -----------------
> From: Richard Boulanger rboulanger@berklee.edu
> Date: Fri, 11 Feb 2005 11:01:08 -0500
> To: csound-devel@lists.sourceforge.net
> Subject: [Cs-dev] Question About the Organization of the Csound Sources
> 
> 
> Dear Developers,
> 
> I may be way off here and please forgive me if I am, but since there is
this

> incredible effort to organize and include all things in Csound5 and make
the
> code simpler to study, expand, etc, why is it that we continue to group so
> many of the older ugens into ugens1.c - ugensB.c - rather than separate
> opcodes into .c and .h files and/or folders
> 
> I am sure that these are referenced in many many files and that it would
> mean checking for, changing and fixing many busted #includes, and then
there
> would need to be changes in all these great makefiles that are currently
> working.....
> 
> but wouldn't it be so much clearer to have each of the opcodes in a
separate
> file.  Where is convolve.c, foscil.c, loscil.c? (Yes I can find them.) And
> why are they in ugens.x vs ugens.y? And why not in ugens.z?
> 
> It just seems to me that it would be so much clearer and easier to study,
> expand, search, etc... - if you had a folder with all the opcodes .c and
.h
> files - or if you would organize things into folders such as the oscil
> family, the filter family, the envelope family, the ftable family, etc...
> 
> Here today for example, I am looking for the "transeg" sources.  And using
> jedit on my Mac, I am able to look into all the files and find that it is
> located in pitch.c (in the 4.23f8 sources).  What exactly does it have to
do
> with "pitch?"
> 
> I bet you have already cleaned all this up in the Csound5 sources.  If
this
> is the case, then please forgive me for asking this ridiculous question,
but
> if you have not done this level of re-organization, I think it would be
> incredibly helpful to students especially, and to teachers without a clue
-
> suffering on a Macintosh OS - such as me, if you would consider doing it.
> 
> Thanks,
> 
> -Dr. B.
> _______________________________________________________________________
> +  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
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> 
> 
> 
> -------------------------------------------------------
> 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_ide95&alloc_id396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

_______________________________________________________________________
 +  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

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .




-------------------------------------------------------
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_ide95&alloc_id396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael,

I would be happy to do it myself.

It seems that this would be a good thing for the future developers -
 
If there is some interest, once I finish,  Who of the current developers
would fix the makefiles and the includes?

Rick

I would on 2/11/05 1:31 PM, gogins@pipeline.com at gogins@pipeline.com
wrote:

> I don't think most developers are going to be put off by finding this kind
> of mild disorganization. If it's important to you, perhaps you could get
> one of your students to become a Csound developer and factor out the
> sources into one opcode per .c file.
> 
> Original Message:
> -----------------
> From: Richard Boulanger rboulanger@berklee.edu
> Date: Fri, 11 Feb 2005 12:03:28 -0500
> To: csound-devel@lists.sourceforge.net
> Subject: Re: [Cs-dev] Question About the Organization of the Csound Sources
> 
> 
> I understand what you are saying.  That's cool and thanks for the tip.
> 
> It worked here on my Mac in the Terminal.  Cool.  (I need to learn grep for
> sure.)
> 
> BUT...
> 
> Doesn't it make sense, that in this wonderful effort to cleanup, organize,
> etc. that you might help future developers and especially students/teachers,
> to not require them to hunt for everything? Why not "standardize" the
> sources and just reveal what is "in" Csound.
> 
> Or
> 
> Why not just put everything in opcodes.c and opcodes.h?
> 
> Why are some here and some there? And why are some separate and some grouped
> into groups that have no logical affiliation?
> 
> Isn't this one of the very things that ALWAYS frustrated new developers
> about Csound - that it took them a few hours/days to figure out what was
> there and how things were "organized." (if at all).
> 
> Rick
> 
> 2/11/05 11:48 AM, gogins@pipeline.com at gogins@pipeline.com wrote:
> 
>> I will always prefer to fix bugs or add new functionality, over fixing
> what
>> is not broken.
>> 
>> Anyone who wants to find anything in Csound 5 only has to go to the
> csound5
>> directory and:
>> 
>> grep findthis */*.c
>> 
>> Original Message:
>> -----------------
>> From: Richard Boulanger rboulanger@berklee.edu
>> Date: Fri, 11 Feb 2005 11:01:08 -0500
>> To: csound-devel@lists.sourceforge.net
>> Subject: [Cs-dev] Question About the Organization of the Csound Sources
>> 
>> 
>> Dear Developers,
>> 
>> I may be way off here and please forgive me if I am, but since there is
> this
> 
>> incredible effort to organize and include all things in Csound5 and make
> the
>> code simpler to study, expand, etc, why is it that we continue to group so
>> many of the older ugens into ugens1.c - ugensB.c - rather than separate
>> opcodes into .c and .h files and/or folders
>> 
>> I am sure that these are referenced in many many files and that it would
>> mean checking for, changing and fixing many busted #includes, and then
> there
>> would need to be changes in all these great makefiles that are currently
>> working.....
>> 
>> but wouldn't it be so much clearer to have each of the opcodes in a
> separate
>> file.  Where is convolve.c, foscil.c, loscil.c? (Yes I can find them.) And
>> why are they in ugens.x vs ugens.y? And why not in ugens.z?
>> 
>> It just seems to me that it would be so much clearer and easier to study,
>> expand, search, etc... - if you had a folder with all the opcodes .c and
> .h
>> files - or if you would organize things into folders such as the oscil
>> family, the filter family, the envelope family, the ftable family, etc...
>> 
>> Here today for example, I am looking for the "transeg" sources.  And using
>> jedit on my Mac, I am able to look into all the files and find that it is
>> located in pitch.c (in the 4.23f8 sources).  What exactly does it have to
> do
>> with "pitch?"
>> 
>> I bet you have already cleaned all this up in the Csound5 sources.  If
> this
>> is the case, then please forgive me for asking this ridiculous question,
> but
>> if you have not done this level of re-organization, I think it would be
>> incredibly helpful to students especially, and to teachers without a clue
> -
>> suffering on a Macintosh OS - such as me, if you would consider doing it.
>> 
>> Thanks,
>> 
>> -Dr. B.
>> _______________________________________________________________________
>> +  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
>> 
>> --------------------------------------------------------------------
>> mail2web - Check your email from the web at
>> http://mail2web.com/ .
>> 
>> 
>> 
>> 
>> -------------------------------------------------------
>> 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_ide95&alloc_id396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> _______________________________________________________________________
> +  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
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> 
> 
> 
> -------------------------------------------------------
> 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_ide95&alloc_id396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

_______________________________________________________________________
 +  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

For Instance...

I am looking right now for the source of the buzz opcode.

The grep trick below can't seem to find buzz.c anywhere

In entry1 I find the prototype (in the opcode list table) and I do find it's
initialization function bzzset

But 

Grep doesn't find any other refs in this directory.

Using jEdit again... I do find it in ugens4.c but I am proposing that one
should not have to hunt all over to get a sense of ALL the great stuff in
Csound.

Rick


on 2/11/05 1:46 PM, Richard Boulanger at rboulanger@berklee.edu wrote:

> Michael,
> 
> I would be happy to do it myself.
> 
> It seems that this would be a good thing for the future developers -
> 
> If there is some interest, once I finish,  Who of the current developers
> would fix the makefiles and the includes?
> 
> Rick
> 
> I would on 2/11/05 1:31 PM, gogins@pipeline.com at gogins@pipeline.com
> wrote:
> 
>> I don't think most developers are going to be put off by finding this kind
>> of mild disorganization. If it's important to you, perhaps you could get
>> one of your students to become a Csound developer and factor out the
>> sources into one opcode per .c file.
>> 
>> Original Message:
>> -----------------
>> From: Richard Boulanger rboulanger@berklee.edu
>> Date: Fri, 11 Feb 2005 12:03:28 -0500
>> To: csound-devel@lists.sourceforge.net
>> Subject: Re: [Cs-dev] Question About the Organization of the Csound Sources
>> 
>> 
>> I understand what you are saying.  That's cool and thanks for the tip.
>> 
>> It worked here on my Mac in the Terminal.  Cool.  (I need to learn grep for
>> sure.)
>> 
>> BUT...
>> 
>> Doesn't it make sense, that in this wonderful effort to cleanup, organize,
>> etc. that you might help future developers and especially students/teachers,
>> to not require them to hunt for everything? Why not "standardize" the
>> sources and just reveal what is "in" Csound.
>> 
>> Or
>> 
>> Why not just put everything in opcodes.c and opcodes.h?
>> 
>> Why are some here and some there? And why are some separate and some grouped
>> into groups that have no logical affiliation?
>> 
>> Isn't this one of the very things that ALWAYS frustrated new developers
>> about Csound - that it took them a few hours/days to figure out what was
>> there and how things were "organized." (if at all).
>> 
>> Rick
>> 
>> 2/11/05 11:48 AM, gogins@pipeline.com at gogins@pipeline.com wrote:
>> 
>>> I will always prefer to fix bugs or add new functionality, over fixing
>> what
>>> is not broken.
>>> 
>>> Anyone who wants to find anything in Csound 5 only has to go to the
>> csound5
>>> directory and:
>>> 
>>> grep findthis */*.c
>>> 
>>> Original Message:
>>> -----------------
>>> From: Richard Boulanger rboulanger@berklee.edu
>>> Date: Fri, 11 Feb 2005 11:01:08 -0500
>>> To: csound-devel@lists.sourceforge.net
>>> Subject: [Cs-dev] Question About the Organization of the Csound Sources
>>> 
>>> 
>>> Dear Developers,
>>> 
>>> I may be way off here and please forgive me if I am, but since there is
>> this
>> 
>>> incredible effort to organize and include all things in Csound5 and make
>> the
>>> code simpler to study, expand, etc, why is it that we continue to group so
>>> many of the older ugens into ugens1.c - ugensB.c - rather than separate
>>> opcodes into .c and .h files and/or folders
>>> 
>>> I am sure that these are referenced in many many files and that it would
>>> mean checking for, changing and fixing many busted #includes, and then
>> there
>>> would need to be changes in all these great makefiles that are currently
>>> working.....
>>> 
>>> but wouldn't it be so much clearer to have each of the opcodes in a
>> separate
>>> file.  Where is convolve.c, foscil.c, loscil.c? (Yes I can find them.) And
>>> why are they in ugens.x vs ugens.y? And why not in ugens.z?
>>> 
>>> It just seems to me that it would be so much clearer and easier to study,
>>> expand, search, etc... - if you had a folder with all the opcodes .c and
>> .h
>>> files - or if you would organize things into folders such as the oscil
>>> family, the filter family, the envelope family, the ftable family, etc...
>>> 
>>> Here today for example, I am looking for the "transeg" sources.  And using
>>> jedit on my Mac, I am able to look into all the files and find that it is
>>> located in pitch.c (in the 4.23f8 sources).  What exactly does it have to
>> do
>>> with "pitch?"
>>> 
>>> I bet you have already cleaned all this up in the Csound5 sources.  If
>> this
>>> is the case, then please forgive me for asking this ridiculous question,
>> but
>>> if you have not done this level of re-organization, I think it would be
>>> incredibly helpful to students especially, and to teachers without a clue
>> -
>>> suffering on a Macintosh OS - such as me, if you would consider doing it.
>>> 
>>> Thanks,
>>> 
>>> -Dr. B.
>>> _______________________________________________________________________
>>> +  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
>>> 
>>> --------------------------------------------------------------------
>>> mail2web - Check your email from the web at
>>> http://mail2web.com/ .
>>> 
>>> 
>>> 
>>> 
>>> -------------------------------------------------------
>>> 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_ide95&alloc_id396&op=click
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>> _______________________________________________________________________
>> +  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
>> 
>> --------------------------------------------------------------------
>> mail2web - Check your email from the web at
>> http://mail2web.com/ .
>> 
>> 
>> 
>> 
>> -------------------------------------------------------
>> 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_ide95&alloc_id396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> _______________________________________________________________________
> +  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

_______________________________________________________________________
 +  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

Why not create a text file that lists opcodes and the corresponding
source files ?


-------------------------------------------------------
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

Istvan,

Great idea.

That would be an excellent quickFix, but don't you think that the codeBase
would be more impressive - and at the same time - less daunting - if one
could look into a folder and see all the opcodes, gens, and utilities listed
and organized alphabetically?

I for one would LOVE it.

Dr. B.

 could really on 2/11/05 3:18 PM, Istvan Varga at istvan@csounds.com wrote:

> Why not create a text file that lists opcodes and the corresponding
> source files ?
> 
> 
> -------------------------------------------------------
> 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

_______________________________________________________________________
 +  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

There's a list, but I'm not sure if it's complete called
Loadable_Opcodes.txt on the root sources directory.

Andrés

Istvan Varga wrote:
> Why not create a text file that lists opcodes and the corresponding
> source files ?
> 
> 
> -------------------------------------------------------
> 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

Istvan Varga wrote:
> Why not create a text file that lists opcodes and the corresponding
> source files ?

If an experienced developer did this then it should be possible for 
someone with a bit more time available (and less knowledge) to pick that 
up and use it as a basis for a unification of the opcodes into one file 
or a division of the opcodes into individual files.

Jon Stutters


-------------------------------------------------------
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

The simple way to find the source of an opcode is to grep
for the name in Engine/entry*.c and Opcode/*.c
  Then use of the TAGS file finds the source simply with C-X-. 
You are of course using emacs


They is a great deal to be said for continuity, at least from the
developer POV

==John ffitch


-------------------------------------------------------
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

On 2/12/05 3:08 PM, jpff@codemist.co.uk  etched in
stone:

> The simple way to find the source of an opcode is to grep
> for the name in Engine/entry*.c and Opcode/*.c
> Then use of the TAGS file finds the source simply with C-X-.
> You are of course using emacs
> 

Well, I don't use emacs but I do exactly the same thing in CodeWarrior when
I am looking for an opcode.  I will admit that it is a little bit
inconvenient and I have often thought that there is very little logic to the
source files' organization.  (e.g. You would think that the pluck opcode is
in pluck.c, but you would be wrong).

> They is a great deal to be said for continuity, at least from the
> developer POV

However, I am going to have to side with John on this one.  I feel that a
massive reorganization of the current source files (and the proposed changes
are huge) would actually be counter-productive to the goal of integrating
and synchronizing the "other Csounds" -- like AV and MacCsound -- with what
is in CVS.  And it will make transfering bug fixes from Cs4 to Cs5 (which
will have to be done eventually) much more difficult.

I also do not want to see a file for every single opcode in Csound.  There
are over 600 opcodes with unique names currently.  IF the reorganization
were to occur, I would beg whoever is doing it to please put families of
opcodes and related opcodes in the same files.

Yes, reorganization would make entry into Csound development easier.  But I
believe it would make the current foci of development considerably more
difficult.  Perhaps it could be done sometime in the future after Csound 5
becomes the standard upon which all versions are based.

In the meantime, an up-to-date "guide to the code for new developers" would
be good enough in my opinion.

(Sorry to write so much about this topic, but I thought John's argument
might have left too much unsaid :)

Anthony



-------------------------------------------------------
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

For now,

A Guide to the Csound Opcodes would be a plus.  In the future, I do hope
that someone will put them all in separate files or families of files that
make more sense.

-Dr. B.

on 2/17/05 12:25 AM, Anthony Kozar at anthony.kozar@utoledo.edu wrote:

> On 2/12/05 3:08 PM, jpff@codemist.co.uk  etched in
> stone:
> 
>> The simple way to find the source of an opcode is to grep
>> for the name in Engine/entry*.c and Opcode/*.c
>> Then use of the TAGS file finds the source simply with C-X-.
>> You are of course using emacs
>> 
> 
> Well, I don't use emacs but I do exactly the same thing in CodeWarrior when
> I am looking for an opcode.  I will admit that it is a little bit
> inconvenient and I have often thought that there is very little logic to the
> source files' organization.  (e.g. You would think that the pluck opcode is
> in pluck.c, but you would be wrong).
> 
>> They is a great deal to be said for continuity, at least from the
>> developer POV
> 
> However, I am going to have to side with John on this one.  I feel that a
> massive reorganization of the current source files (and the proposed changes
> are huge) would actually be counter-productive to the goal of integrating
> and synchronizing the "other Csounds" -- like AV and MacCsound -- with what
> is in CVS.  And it will make transfering bug fixes from Cs4 to Cs5 (which
> will have to be done eventually) much more difficult.
> 
> I also do not want to see a file for every single opcode in Csound.  There
> are over 600 opcodes with unique names currently.  IF the reorganization
> were to occur, I would beg whoever is doing it to please put families of
> opcodes and related opcodes in the same files.
> 
> Yes, reorganization would make entry into Csound development easier.  But I
> believe it would make the current foci of development considerably more
> difficult.  Perhaps it could be done sometime in the future after Csound 5
> becomes the standard upon which all versions are based.
> 
> In the meantime, an up-to-date "guide to the code for new developers" would
> be good enough in my opinion.
> 
> (Sorry to write so much about this topic, but I thought John's argument
> might have left too much unsaid :)
> 
> Anthony
> 
> 
> 
> -------------------------------------------------------
> 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

_______________________________________________________________________
 +  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