Messages in this thread | | | Subject | Re: [PATCH] headers_check: special case seqbuf_dump() | From | Paul Bolle <> | Date | Thu, 16 Jan 2014 13:39:24 +0100 |
| |
On Thu, 2014-01-16 at 12:53 +0100, Takashi Iwai wrote: > At Wed, 15 Jan 2014 11:48:19 +0100, > Paul Bolle wrote: > > 2) By the way, what is actually meant by: > > It is no longer possible to actually link against OSSlib with this > > header, but we still provide these macros for programs using them. > > > > Doesn't that mean compatibility to OSSlib isn't even useful? > > Well, it's not about the compatibility to osslib. The OSS seq > user-space codes are written with these macros no matter whether to > use osslib or not. osslib was newer than these macros and it was > designed to be compatible with them.
So perhaps that line should read something like: [...] header, but we still provide these macros for programs that want to interface with /dev/dsp and /dev/sequencer directly.
I'm making that up: I know nothing about this stuff. I'm just looking for a way to make that comment clear to a person that wonders in, say, 2019: "What on earth is seqbuf_dump() good for?".
Paul Bolle
| |