Talk:cpp/io/c/fwscanf

Given that this looks like part of a rather sweeping set of changes, maybe it's worth discussing a bit to get some consensus on how this should work. Specifically, I'm wondering about (1) what the goal is of the root level /c/ section and (2) changing things in the /cpp/ section to be more C-specific (e.g. changing a header from cstdio to stdio.h).

I'm curious and not necessarily opposed to adding C-specific material to the site, but we want to make sure we do it in a planned and consistent way that will make sense to our users. Thoughts? Nate 12:27, 13 April 2012 (PDT)

Hi. I added the /c/ root section for C-specific material. I though about various options and putting everything under /c/ looked like the most reasonable one. This way, the C++ reference is contained within /cpp/ root section and C reference is at /c/ with little coupling between the two. As for the changes in /cpp/, they were unintentional. In fact, I think there's no reason to keep anything C specific in the /cpp/ section. Eendy 13:57, 13 April 2012 (PDT)

I think what Eendy has done fits into the current structure quite well. I've actually envisaged something like this when designing the layout of this wiki - C++ stuff goes to cpp/*, C stuff goes to c/* and so on. -- P12 17:28, 13 April 2012 (PDT)