Post by thread:PIC Routines

Thanks for the input David, If you don't mind, I'll happily add your positive comments to the FAQ but I think at this early stage, I'll reserve the negatives to avoid starting any "my choice is better than your choice" wars. :-) On the code library front, what I suggest is this ; We define a communal "header file" so that all code snippets can refer to the same set of "fixed variables" So that Timer_1, Timer_2, Temp_1, et. al. are defined as to address in the header file and as to function in a seperate specification sheet which we can expand to cover most eventualities. My reasoning is that we all at some time or other need a bit of code to, for instance, Interface to an E2prom, read a keyboard or whatever else you can think of. Now there are almost as many different ways of doing each of these as there are people wanting to do them. One routine will be fastest, the next will use fewer mem. locs. the next will take up less prog. space, while another will use fewer input pins. Now, would'nt it be nice if all these routines were available by e-mail and you had a copy of an index for them ? I mean not only the best routine that you could come up with, when the job was required `yesterday', but the best that the distilled wisdom of the pic-literate world is capable of ! I'm setting up an automatic mailling service to do just that. The way it will work is as follows ; You need a routine for a specific function say "function_X" You send mail to "spam_OUTpic_funcTakeThisOuTtakdsign.demon.co.uk" with "function_X" as the subject. The latest version of "function_X" will be e-mailled to you. If while working with it you come up with a mod to the function, you re-write it and mail it back with your justification for the mod and I add it to the list. If all the pic users do this............!!! Think of it as "electronic software evolution" :-).......OR if you think the idea is a load of cr*p, let's hear your suggestions. BTW do you subscribe to the pic mailling group ?