Hello,
Are we allowed to write custom libraries for RobotC?
If yes, then where are we supposed to dump it, I mean the .c and .h files.
Any words of wisdom?
-
Aravind

I've been writing drivers for ROBOTC for a while now and I publish them on my own site (see my signature). My word of wisdom would be to put everything in the header file and not use .c files at all. ROBOTC does not have a linker, so you'd end up with something like #include "somefile.c" and that just looks nasty.
Also, use Doxygen to create auto-documenting code. Take a look at my library to see how I've been doing it.

- Xander

In my project (see my signature) I split code into many .c and .h that all follow strict rules to be compatible with RobotC environment.
Have a look on it and ask questions if necessary

Regards
Miki

When you said "allowed", what context are you referring to? Are you talking about FTC? If you are just doing robot programming on your own, of course you are allowed to do anything to your code. If for FTC, I believe as long as it is publicly available to other teams, it is allowed. We did our own library and it is available here. http://proj.titanrobotics.net/hg/Ftc/2012/code/file/e28dbb95c68b/ftclib
Just like what Xander said, our library is implemented as .h files. Although RobotC doesn't really support object-oriented programming, our library code is organized as objects using C-structures.

Wow, nice job.

Hello,
Thank you Xander, Miki and MHTS. I will look through your sample library files.
@ MHTS: By mentioning "allowed" I meant whether we need an official permission to include such custom libraries into the software. Well anyways I got your point.
Thanks again
-
Aravind