What am I missing here? Beep (412, 100) ==> MessageBeep ((unsigned)-1) and we're done, right? No need for any CYGWIN= hoobajoob or another static BOOL or anything.
-- Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 > On Thu, Feb 13, 2003 at 10:32:47PM -0000, Max Bowsher wrote: > >> I don't like to introduce lots of unnecessary decision > points into a > >> product. It increases support and it increases code complexity. > > > >Complexity? Slightly, but only at CYGWIN-parsing time, and > Beeping time. > >That's not that much, surely? > > This is a cumulative thing. Every "it's only a couple of lines" adds > up. It's a couple lines of code, a couple of extra lines in > documentation, a couple of extra email messages with people struggling > to use it. > > I don't mind adding the lines when we are moving closer to UNIX > compatibility but I will always push back on adding arbitrary > options to > the CYGWIN environment variable. I'm in good company. My predecessor > did the same thing. > > >>Once again, how does linux handle this scenario? You don't do a > >>"export LINUX=linbeep" to get linux to use the soundcard. > > > >If Vaclav is correct - that it required a kernel module - I > think this > >question is answered. > > Ok. How about if I say "I don't think it requires a kernel module". > Does that put things back on course? > > cgf
