Given some of the top voted answers in the last discussion about resource requests and the close votes and flags from other members of the community against your question, it appears that people want to see a bigger emphasis on questions about problems rather than resource requests (even a request for the "canonical reference"). Questions should be about solving a problem, and links to resources should be part of good answers, along with experiences of other users.
However, prior to closing (as I mentioned in my comment), I did a Google search for "object-oriented C" (without quotation marks) and received numerous results. A precursor to asking a question should be to search for an answer, using your favorite search engine and on any relevant Stack Exchange sites. A question should address why these resources aren't sufficient for solving your problem.
From the FAQ:
You should only ask practical, answerable questions based on actual problems that you face.
Below are two excerpts from the answers that are tied for top answer in the question I linked to above. As of now, both have 8 up votes and 0 down votes from members of the community.
From Mark Trapp's top answer in the linked question:
The problem with these questions aren't that they are asking for a book, it's that they don't describe anything about the problem the user is having, or rather why the user is asking the question, to afford a useful response. They're like asking, "tell me what book will teach me everything and anything about Java." Where to begin? Questions must narrow the scope down to a specific problem, otherwise, they don't belong here.
From Robert Harvey's top answer in the linked question:
While I begrudgingly accept the idea that resource requests are on-topic if they are specific enough, people should really be asking "how" questions, not "what" questions