Hi Karl, Paul, Thank you for your feedback.
> I agree with Paul that having it just in a blog entry seems insufficiently > advertised :). Yes, in fact the text I wrote will also be valid and applicable in 5 or 10 years, therefore it's better put into a manual than into a blog. > 3. Since this isn't gnulib specific, I'm not sure about having it in the > gnulib manual. But maybe it could be a new section about programming > in general, especially if you have other topics in mind. There are currently 3 pieces of documentation that deal with C programming: - The glibc manual, - The Autoconf manual's section "Portable C and C++ Programming", - The gnulib manual. For my feeling, the section in the Autoconf manual does not really belong there. Either we should have a separate manual about "Portable C and C++ Programming", or it should be moved to the gnulib manual. Until this separate manual exists, I think the best place is the gnulib manual. > 4. I also agree with Paul about posting a news entry in gnulib with a > url to wherever it ends up (your site or the manual or wherever). Yes, I'll do this, then. > In general, making more use of gnulib's news area (e.g., incompatible > changes, major additions, other milestones) seems like it would be a > good thing. OK. I've enabled the news section on Savannah. News postings can be created by any member of the Gnulib group on Savannah, but are not posted until approved by either Jim or Eric or me. I also sent a news entry about recent new features. Let's see whether it appears on planet.gnu.org. Bruno -- In memoriam Yuri Shchekochikhin <http://en.wikipedia.org/wiki/Yuri_Shchekochikhin>
