Attached are two of the FAQs I wrote. I'm leaving out the multiple files, as whiteflags suggested, and I'm quite alright with parts or all of the extern/static one being merged in with another FAQ if deemed appropriate.
I'm a little confused on the purpose of the cpwiki thing. I mean, looks like it's a wiki to cover common issues here (basically a wiki FAQ), but it's not easily found when looking around this site. I can get an account and get my articles up over there too if everybody wants.
@anduril462: In your Shared Library file, would it be a good idea to introduce ldconfig instead of messing with the environment paths ?
I thought about it, and came to the conclusion that changing LD_LIBRARY_PATH is more versatile. Students who are working on school systems may not have permissions to modify /usr/lib or any of the /etc/ld.so.conf files. I think you're right however. It would be good to cover it for personal systems, for which the programmer has admin rights, and I can cover stuff like "scan the current dir" or "use my personal ld.so.conf" for people who don't have admin rights. Time to get started on v2.
cpwiki was just originally intended as a place to put articles, especially common issues since people grow tired of repeating them. Back then, we couldn't get them on the main site, I believe.Originally Posted by anduril462
Regardless, the fact that we can now put articles on the main site deprecates cpwiki. The articles there should really be ported to the main site.
However, it's still good for writing, editing and discussing articles before porting them to the main site.
@anduril462 These are very good write-ups! I think the static vs extern should be a stand-alone FAQ entry. I will edit the header file FAQ entry to demonstrate example uses of extern and static with a link to this entry, once it's posted. As for shared libraries article, I'm a bit torn as to whether it's a better fit for the FAQ or a standalone article.
I'd like to take this time to also switch the software used for the FAQ; it produces ugly looking URLs and isn't that flexible. It should be possible to have links from the FAQ to articles that appear elsewhere on the site, for situations where there are very in-depth answers to questions and it doesn't make sense to write another FAQ entry on the same topic. That might be the most appropriate thing to do for the shared libraries tutorial. I do think introducing ldconfig makes it a better fit as a standalone article.
@Elysia Let me take a look at what's on the cpwiki and see what would make sense to transfer to the main site, and where it should go. Some things are better as FAQ entries (usually shorter articles that answer a specific question--ex: static vs extern) and some things are better as full articles/tutorials (usually longer/more in-depth writeups, like the GDB tutorial which has an extensive example).
Absolutely.
And note that there are some articles that are duplicates of those on the main site which may need to be merged or simply disposed. Pause console is one that comes to mind, I believe.
