HTML Code Export is a unique and easy to use software to quickly and easily reindent, export (10+ formats supported) and print your html documents. Upgrade your old html pages to xhtml. Convert your html documents to PDF, RTF, images and more!
With the HTML Code Export, you can :
Format / Indent your html code
Convert your html code to the following formats :
Print / Create advanced reports using a state-of-the-art printing / report engine
And much more!
C++ Code Export: http://www.cpptalk.net/cpp-code-export/cpp_export.zip
HTML Code Export: http://www.highdots.com/html-code-export/html_export.zip
Project Analyzer is a Visual Basic source code analyzer, optimizer and documenter. It works with VB, VB.NET, ASP.NET and Office VBA. Project Analyzer does an automatic code review to detect quality control issues like dead code, unoptimal variable declarations, unoptimized syntax, memory leaks and functionality issues such as missing event handlers or questionable tab order. You can enforce programming standards on variable naming, commentation, disallowed statements and code complexity. Optionally, you can let the tool automatically remove or comment out the unused, dead code to considerably reduce the size of your program. You can also search for duplicated code blocks that frequently result from copy-paste coding.
Project Analyzer lets you navigate your projects with hypertext and graphical views. Click objects to see their use and declarations. Locate code via the enhanced Find window. Copy syntax-formatted code to documents. Understand existing programs with the help of cross-references, call trees, called-by trees, class diagrams, dependency diagrams and Visio diagramming support.
Project Analyzer generates comprehensive project documentation, including source code listings, comment manuals, cross-reference listings, module reports, project dictionary. It can turn VB code into a web site or linked PDF. Besides source code analysis, the program also analyzes binary DLL and COM libraries. Project Analyzer calculates 180 software metrics including lines of code, cyclomatic complexity, relative complexity, depth of conditional nesting, amount of commentation and object-oriented metrics for the entire inheritance tree.
Project Analyzer: http://www.aivosto.com/shareware/project.zip
MMX/SSE instructions can greatly enhance the performance of the following applications: multimedia (audio/video), communications, DSP kernels, 2D and 3D graphics, image processing and speech recognition.
But current compilers do not support these instructions.
Now there is a better way: Quexal, a development environment aimed at MMX/iSSE programmers.
Here is how Quexal will help you get the job done quickly and easily:
- flatten the learning curve! you can work with well understood concepts, such as variables and common operations, instead of registers and cryptic MMX/SSE opcodes;
- take it easy! its custom designed graphical interface guides you step by step, displaying only relevant options;
- work faster! the compiler optimizes source code into optimally scheduled MMX/SSE assembly code that can be directly pasted into any other development environment, thus taking the optimization phase, the most time-consuming and error prone one, out of the development cycle;
- save an upgrade! you can use MMX and iSSE instructions even if your compiler does not support them, as the bytecode compiler turns source instructions directly into machine language; Quexal supports the Microsoft Visual C++, Borland C++ Builder and Borland Delphi compilers;
- bug killer! includes a visual Debugger that re-arranges source code in a graph showing dependency bonds among instructions; you can enter source values and analyze what the instructions defined in source code do, and therefore easily detect troublesome spots;
- become a code guru - instantly! the optimized code is as good as that written by world class programmers, but no knowledge of micro architectural designs is required;
- maintaining code? no problem! you can modify the source code in the Quexal environment and then optimize it again, instead of changing MMX/iSSE code listings.