Rosetta Code:Village Pump/LibRC, A Library for RosettaCode Code
This is a particular discussion thread among many which consider Rosetta Code.
Summary
I wish to take all the code segments on RosettaCode that can be libified and turn all of it into a one-stop shop library for anyone to use. (The only problem is I don't know some of the languages on here and so need contributors!)
Discussion
Hello all, I wish to create a library, called LibRC, that will contain all the code segments that can be turned into a library code fragment and turn them into a code fragment. I can take all of the C, C++, Fortran, Go, Java, Objective-C, and Objective-C++ ones because I compiled, myself, a copy of all the GCC 6.1.0 languages (accept Ada because Gentoo's Ada compiler won't emerge properly) and so I can't compile that one. The library name is LibRC, but I can change it if you like. (I haven't even managed to compile it all yet!) I would like to also discuss possible naming schemes for the library files, if this is an accepted project by everyone. Here's a possible one that I just thought of: Ada: librcada.so (-lrcada in GCC) C: librcc.so (-lrcc in GCC) C++: librccpp.so (-lrccpp in GCC) Fortran: librcfortran.so (-lrcfortran in GCC) Go: librcgo.so (-lrcgo in GCC) Java: librcjava.so (-lrcjava in GCC) Objective-C: librcobjc.so (-lrcobjc in GCC) Objective-C++: librcobjcpp.so (-lrcobjcpp in GCC) Of course, I'm willing to change this if you guys think that this is an inadequate or protracted naming scheme. (I'm not sure how we'll compile the interpreted languages like Make, CMake, etc.) So, what do you guys think? If you want to help me with this project, simply say so and I'll work on adding you to the development team! (Or, you can even suggest other methods of working on this!)
- So we will have both support for 99 bottles of beer on the wall and for sleep sort in the same library?
- I joke, but so does some of the code...
- Anyways, if getting that to compile sounds like an interesting task. But before you spend too much time organizing, I think I would try to characterize some of the difficulties and some of the hardware dependencies that you care about.
- More than that, though, the primary benefit of Rosetta code is having something that people can read and compare. (But making sure all the code compiles is important - I know that I myself have sometimes come back later and found that code that I had written did not work, because I had either not made an edit or some other stupid mistake.)
- Still, if you also mean for this library to be of use to other people you would need to spend some time thinking about those people's needs and how to document the library and its use for them. The easy thing to do (just link to the site) will work about like just pulling down all the code samples and trying to compile them together.
- Anyways, *we* need efforts like yours, to help us isolate our problems. But I expect that most of the resulting library would mostly not be things most other people need. Still, the skills you might develop, working through this, might turn out to be useful to you, in other contexts.
- But I would not worry about the naming, either, I guess...