[Csound] reading source code
Date | 2015-10-18 09:46 |
From | Zohar Argaman |
Subject | [Csound] reading source code |
Hi
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
i'm interested in knowing how DCBlock2 is implemented. is there a way to look at the source code? thanks |
Date | 2015-10-18 10:02 |
From | Victor Lazzarini |
Subject | Re: [Csound] reading source code |
Here it is Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland
|
Date | 2015-10-18 18:21 |
From | Tarmo Johannes |
Subject | Re: [Csound] reading source code |
Hi,
Steven mentioned, it is really easy to find the file and place inthe sources for an opcode, using some grep and probably find commands. Please reveal (and perhaps write somewhere in knowledge base or README) how to do it?
ie. give a fishing the rod to a hungry man, not fish :)
Thanks! tarmp
On Sunday 18 October 2015 10:02:47 you wrote: > Here it is > https://github.com/csound/csound/blob/develop/Opcodes/dcblockr.c > > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > > > On 18 Oct 2015, at 09:46, Zohar Argaman <zoharargaman@GMAIL.COM> wrote: > > > > Hi > > > > i'm interested in knowing how DCBlock2 is implemented. is there a way to > > look at the source code? > > > > thanks > > Csound mailing list Csound@listserv.heanet.ie > > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > > https://github.com/csound/csound/issues Discussions of bugs and features > > can be posted here > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here
|
Date | 2015-10-18 18:46 |
From | jpff |
Subject | Re: [Csound] reading source code |
If you ave the sioures locally I use a combination of etags anf a local cimmany called Search wich is grep $1 $2 `cat all_string_files` But I am an inveterant cmmand line =emacs user, te only way to go...... On Sun, 18 Oct 2015, Tarmo Johannes wrote: > > Hi, > > > > Steven mentioned, it is really easy to find the file and place inthe sources > for an opcode, using some grep and probably find commands. Please reveal (and > perhaps write somewhere in knowledge base or README) how to do it? > > > > ie. give a fishing the rod to a hungry man, not fish :) > > > > > > Thanks! > > tarmp > > > > On Sunday 18 October 2015 10:02:47 you wrote: > > > Here it is > > > https://github.com/csound/csound/blob/develop/Opcodes/dcblockr.c > > > > > > > > > Victor Lazzarini > > > Dean of Arts, Celtic Studies, and Philosophy > > > Maynooth University > > > Ireland > > > > > > > On 18 Oct 2015, at 09:46, Zohar Argaman |
Date | 2015-10-18 19:19 |
From | jpff |
Subject | Re: [Csound] reading source code |
Thanks!
what do $1 and $2 stand for?
I tried grep websocket `cat all_string_files` on command line and indeed, it gives already a glue but $2 could probably refine the search.
tarmo
> If you ave the sioures locally I use a combination of etags anf a local > cimmany called Search wich is > grep $1 $2 `cat all_string_files` > > But I am an inveterant cmmand line =emacs user, te only way to go......
On Sun, 18 Oct 2015, Tarmo Johannes wrote:
> > Hi, > > > > Steven mentioned, it is really easy to find the file and place inthe sources > for an opcode, using some grep and probably find commands. Please reveal (and > perhaps write somewhere in knowledge base or README) how to do it? > > > > ie. give a fishing the rod to a hungry man, not fish :) > > > > > > Thanks! > > tarmp > > > > On Sunday 18 October 2015 10:02:47 you wrote: > > > Here it is > > > https://github.com/csound/csound/blob/develop/Opcodes/dcblockr.c > > > > > > > > > Victor Lazzarini > > > Dean of Arts, Celtic Studies, and Philosophy > > > Maynooth University > > > Ireland > > > > > > > On 18 Oct 2015, at 09:46, Zohar Argaman <zoharargaman@GMAIL.COM> wrote: > > > > > > > > Hi > > > > > > > > i'm interested in knowing how DCBlock2 is implemented. is there a way to > > > > look at the source code? > > > > > > > > thanks > > > > Csound mailing list Csound@listserv.heanet.ie > > > > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > > > > https://github.com/csound/csound/issues Discussions of bugs and features > > > > can be posted here > > > Csound mailing list > > > Csound@listserv.heanet.ie > > > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > > > Send bugs reports to > > > https://github.com/csound/csound/issues > > > Discussions of bugs and features can be posted here > > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here >
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2015-10-18 20:20 |
From | jpff |
Subject | Re: [Csound] reading source code |
$1issubstituted by te fuirst argument and $2 the second So Seach websocket woud be equivalent to what you typed. $2 just allows more comlex searches -- actually /i very rarely use. I use earch to find where to start. Ren in emacs M-. finds functions and struct definitions. No idea how to navigate via a desktop. I also cheat, just knowing a lot if te code ==John On Sun, 18 Oct 2015, jpff wrote: > > Thanks! > > > > what do $1 and $2 stand for? > > > > I tried > > grep websocket `cat all_string_files` > > on command line and indeed, it gives already a glue but $2 could probably > refine the search. > > > > tarmo > > > > > If you ave the sioures locally I use a combination of etags anf a local > > > cimmany called Search wich is > > > grep $1 $2 `cat all_string_files` > > > > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2015-10-19 14:23 |
From | Steven Yi |
Subject | Re: [Csound] reading source code |
Hi Tarmo, I usually go into the root of the Csound directory and type grep "what to find" * -n -r And that recursively finds the text in files in subdirectories and also reports line numbers in the file. I may also limit it to Opcodes/* or Oops/* if I have an idea of what subfolder it is in. Steven On Sun, Oct 18, 2015, 1:22 PM Tarmo Johannes <tarmo.johannes@otsakool.edu.ee> wrote:
|
Date | 2015-10-19 16:18 |
From | Tarmo Johannes |
Subject | Re: [Csound] reading source code |
Thank you!
I saved both this the one John suggested to a .sh script and no more puzzleing!
tarmo
On Monday 19 October 2015 13:23:15 you wrote: > grep "what to find" * -n -r
|