Allows to turn standard R code into offensive programming code. 
    Provides code instrumentation to ease this change and tools to assist and 
    accelerate code production and tuning while using offensive programming code 
    technics. 
    Should improve code robustness and quality. Function calls can be easily 
    verified on-demand or in batch mode to assess parameter types and length 
    conformities. 
    Should improve coders productivity as offensive programming reduces the code
    size due to reduced number of controls all along the call chain. 
    Should speed up processing as many checks will be reduced to one single check.

Allows to generate on-demand or by batch, any R documentation file,
    whatever is kind, data, function, class or package. It populates
    documentation sections, either automatically or by considering
    your input. Input code could be standard R code or offensive programming code. 
    Documentation content completeness depends on the type of code you use. With
    offensive programming code, expect generated documentation to be fully 
    completed, from a format and content point of view. With some standard R 
    code, you will have to activate post processing to fill-in any section that 
    requires complements. Produced manual page validity is automatically tested 
    against R documentation compliance rules. Documentation language 
    proficiency, wording style, and phrasal adjustments remains your job.

Allows to generate automatically 'testthat' code files from offensive 
    programming test cases. Generated test files are complete and ready to run.
    Using 'wyz.code.testthat' you will earn a lot of time, reduce the number of
    errors in test case production, be able to test immediately generated files 
    without any need to view or modify them, and enter a zero time latency between 
    code implementation and industrial testing. As with 'testthat', you may
    complete provided test cases according to your needs to push testing further, 
    but this need is nearly void when using 'wyz.code.offensiveProgramming'.