I have not been having noisy output from PortAudio v19, though I did at
first. I believe changing the device number fixed it, or maybe I changed
something in my code; but you should now have my code for this. 

But I will look at this again tonight on Linux, since some code may have
reverted.

On another note, I saw in your CVS log messages something about "code
standards" or "bringing code to standard." Can you tell me what that means?

Original Message:
-----------------
From:  jpff@codemist.co.uk
Date: Mon, 15 Mar 2004 20:30:43 +0000
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4328] Getting in step


I am almost there now.  Just before supper I did manage to compile it
all, but some problems have crept back.  In principle all the
utilities now use linsndfile.  I have tested hetro and a little
others, but will finish the check later.  There are still some
differences between CVS and my files but I am working on them.

On a different note, am I alone is having noisy output from PortAudio?
My standard alias test is unusable with PA.

==John ffitch


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

>>>>> "gogins@pipeline" == gogins@pipeline com  writes:

 gogins@pipeline> On another note, I saw in your CVS log messages
 gogins@pipeline> something about "code standards" or "bringing code
 gogins@pipeline> to standard." Can you tell me what that means?

No tabs; ANSI C according to C89 standard; no lines wider than 80
chars.

Consistent layout.

==John ffitch

Hi John,

Did you mean C99?  Also, are we using 4 spaces for indentation as the
general rule?  (That's what I use these days so I'm wondering.)  And is
there a preferred style for braces?  

Thanks,
steven


On Mon, 2004-03-15 at 23:07, jpff@codemist.co.uk wrote:
> >>>>> "gogins@pipeline" == gogins@pipeline com  writes:
> 
>  gogins@pipeline> On another note, I saw in your CVS log messages
>  gogins@pipeline> something about "code standards" or "bringing code
>  gogins@pipeline> to standard." Can you tell me what that means?
> 
> No tabs; ANSI C according to C89 standard; no lines wider than 80
> chars.
> 
> Consistent layout.
> 
> ==John ffitch
> 
> 

No I did not mean C99.  Not everyone has a C99 compiler.  I mean the 
original ANSI C with was 89 or 90 (the standard is by the University desk 
not this one).  I invested significant time in making it ANSI, and in 
removing tabs with are not the same on all platforms -- multiples of 8 on 
all machines I have used significantly, but of 4 on Windows; at least two 
spaces on Titan, at least 1 on Unix etc.  After discussion it was decided 
that we shoudl not have tabs, so I eliminated them all. They are creeping 
back so in some files I could not read the text as it overflows the line 
length
==John ff

Okay, I was working with the understanding of C99 for some reason.  Glad
to have that clarified!

I too have removed all tabs a month or two ago from my source for blue
as to avoid the varying tabs on different platforms, so it's a bit of
preaching to the choir here. =)  However, I asked about a standard of
how many spaces to use for indentation, if there should be a proposed
standard at all. 

Thanks,
steven



On Mon, 2004-03-15 at 23:29, John ffitch wrote:
> No I did not mean C99.  Not everyone has a C99 compiler.  I mean the 
> original ANSI C with was 89 or 90 (the standard is by the University desk 
> not this one).  I invested significant time in making it ANSI, and in 
> removing tabs with are not the same on all platforms -- multiples of 8 on 
> all machines I have used significantly, but of 4 on Windows; at least two 
> spaces on Titan, at least 1 on Unix etc.  After discussion it was decided 
> that we shoudl not have tabs, so I eliminated them all. They are creeping 
> back so in some files I could not read the text as it overflows the line 
> length
> ==John ff
> 
> 
> 

I have been using
         (c-set-offset 'defun-block-intro 4)
         (setq c-block-comments-indent-p nil)
         (setq c-basic-offset 2)
for ages.

==John ffitch