Optimise and Document C/C++ Geometry functions

This request requires you to submit each of following size (6) functions to the CodeCogs library. We estimate this should take you about 3 hours: \interface bool box_01_contains_point_2d ( double p[2] ); bool box_01_contains_point_nd ( int ndim, double p[] ); bool box_contains_point_2d ( double p1[2], double p2[2], double p[2] ); bool box_contains_point_nd ( int ndim, double p1[], double p2[], double p[] ); void box_ray_int_2d ( double p1[2], double p2[2], double pa[2], double pb[2], double pint[2] ); int box_segment_clip_2d ( double p1[2], double p2[2], double pa[2], double pb[2] ); \endinterface The original source code in contained within a very large file, however all you need to do is extract the relevant pieces, i.e. the 6 functions listed here. We are offering up to a 40% bonus for exceptional documentation. In particular we are keen to see diagrams converted from their current character form into .gif or .jpg. And documentation that is clear, concise and readable by people who are not necessarily experts in the field. ## Deliverables For each routine you must do the following: - Separate each function into a stand-a-lone file header file (*.h). - Function definition and source code should live together in just the header. - If one routine references another, then you should place a #include to link in the relevant dependent file, which should also be in is own file. Function that you don't feel should be listed as distinct modules on codecogs can be group with the main function within one file. - Optimise the source code. See [login to view URL] for suggestions. - Document the module. This is major task, which requires you to tidy up the existing good documentation to make use of the Doxygen markup tags, including adding graphs and figures. Equations should be converted to latex and we expect you to make suitable use of bold and italics etc, to add clarity to the documentation. See [login to view URL] "Documentation Commands" for a complete list of commands you may use. - An examples. For each main function you submit, you should include a simple example which shows how to use the function, with example output. The example should be complete with int main()etc. You should also use this step to ensure the code compiles. It will be tested against gnu C++ and Microsoft C++. - The submitted code must compatible with the CodeCogs submissions system, so they can be automatically added to this library. In addition: 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Unix and Window.