Yes I know it's so strange for most of you. My ambition, if we want to
call it like that, is to find inside source codes (VB6 for the moment
because it's quite simple) cases of obvious risks of failure.
It happens that most developpers don't mind about limit cases like
overflow or underflow. So I started thinking how can I detect such
cases. By the end, I have published the results of my work on my web
site. Still it's not finished.
I encourage you to have a look to :
the principles :
http://d.cr.free.fr/indexen0101.html,
variables (http://d.cr.free.fr/indexen010101.html),
operators (http://d.cr.free.fr/indexen010102.html),
conditions (http://d.cr.free.fr/indexen010103.html),
control structures (http://d.cr.free.fr/indexen010104.html),
functions and subroutines (http://d.cr.free.fr/indexen010105.html),
complete VB6 language syntax strictly no documentation is available on
this...
http://d.cr.free.fr/indexen010106.html)
the simple example :
http://d.cr.free.fr/indexen0102.html
two complex examples :
http://d.cr.free.fr/indexen0103.html see in
particular OpenSource projet CryptoPad
(http://d.cr.free.fr/wswebconsulterfichiers.php?projet=cryptopad) and
BOM (http://d.cr.free.fr/wswebconsulterfichiers.php?projet=bom). See
the original source code in column 1, the formated code and complete
screen appearance in case of FRM file coming from the XML file in
column 2, and the corrected code in last column
Of course, I can understand your reactions against the VB6 addin. Don't
be afraid. I don't bother about the code itself. I don't want to steal
anything to anyone. Indead it can be freightening for a commercial
goal. I'll think about this point later. But still, I can show how it
works one a case study via the VB6 Add-in.
Bye. (the real quality, a goal not so easy to reach...)
Archived from group: microsoft>public>vb>syntax