I wrote a simple parser, which looks for comments inside SQL-Code. If it find a specific remark, the parser store data and generates some output for documentation. There are different types of comments which generates different type of documentation parts. The main idea is to generate a super class with the main methods an derive some class as an implementation for a specific comment type.
This is no problem until here. In the main loop parse the sql-code and had to look, which derived object matches. The parser should try to match each derived object without write down each typename.
Choosing this type of implementation, it will be easy to extend the solution by a new commenttype: Only a new derived class is needed.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.