Naming conventions for function libraries
Anyone have any recommendations for this?
How do you differentiate general resources from app specific?
Web functions from Sql from general?
Re: Naming conventions for function libraries
It doesn't really matter what you do so long as you are consistent across all developers. For app specific libraries, I preface the name with _LIB_[same name as script].
If I had developed an SQL library that was global I might call it _LIB_SQLFuncs or for web _LIB_WebFuncs.
I would just say do whatever is descriptive enough to get the general idea of what's inside the library and easy for you to remember.