Hi.

First, I shell not fail the case to criticize the missing modular organization of the most popular language for programming the largest systems. The first most important rule of design I was taught in the university was "divide and conquer". C lang tries to prove that it is possible to cope complexity without both modules nor hierarchy. It dumps all the files into one big heap. With the help of assembler-derived text include this approach results in 1) You can have Backer str. both in London and Zürich at the same time. But not in c. Because everything is compiled into one big space. 2) Normally, when you have all the ingredients and glue (your code), you can produce an object. But not in c. Once your file compiles successfully in isolation, does not guarantee it will attached to a larger project. 3) Even C++ with its namespaces patch fails to produce a decent development environment. The best tools for C++ are incommensurably ugly compared to the impressing capabilities of development environments for the Java (relatively new language). Even the most advanced C++ dev tools cannot find identifier declarations (for the same reasons that the OP)! Meantime, Java tools can check syntax on the fly why your are typing. This is power of modules. What is simpler for machines, simpler for people. 1) Finally, the compiler is thousands of times slower than pascal, for instance. This is not an exaggeration. This is a feature for compiling especially huge systems, like OSes as a whole. But the perverted c-bigots wrestle the sluggishness of the c compiler turning it into a big advantage by arguing that "it does much more work for the programmer!". Without clarifying which work, of course. Perhaps they mean that c (pre)kompiler, linker and other stuff do good job obfuscating your functions so that the linker you will never know which line of code contains the function which cannot be resolved.

Ok, excuse me for the moralizations. I just want everybody to understand these simple things. I wish some real progress rather than crap in our life and heads wasting our time. Go to the alsa-lib/src/pcm/ directory.

Hi,

I am trying to write an application to just play a wave file and record sound using ALSA --

I looked at the pcm_min.c file and tried to run it - I am using UBUNTU and 1.0.11-7ubuntu3 sound library called libasound2.

I cant seem to find the pcm.c file which has all the snd_pcm_open and other functions used in the pcm_min.c file!

I am using : /usr/include/alsa/asoundlib.h header -- but i m not sure where the functions defined in this header are -- and, find / -name pcm.c yields nothing --nor does find / -name snd_pcm_open

Any pointers please! Thanks, Ashlesha. _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel