Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: Martin_1962 on 05 November 2009, 21:03:48
-
Yesterday I started a test build of our software in the latest version of VO.
How many errors!!!!
Looks like some functions have changed parameter type, others have been strict typed and also some internal ignoring tightened up.
Irritants are
1) All functions and methods must end in RETURN and a value. you have to strict type to use no return value.
Takes ages to set up all the declare and AS VOID STRICTs
2) ACCESS and ASSIGN cannot be same name as any variable in the class or any class the class is based on.
3) Lots of code was using INT and WORD, now wants DWORD, but then later it has to be LONGINT. Agghhhh!
LOads of DWORD(_cast,number) used
I hope to finish this tomorrow!!!!
-
Yesterday I started a test build of our software in the latest version of VO.
How many errors!!!!
Looks like some functions have changed parameter type, others have been strict typed and also some internal ignoring tightened up.
Irritants are
1) All functions and methods must end in RETURN and a value. you have to strict type to use no return value.
Takes ages to set up all the declare and AS VOID STRICTs
2) ACCESS and ASSIGN cannot be same name as any variable in the class or any class the class is based on.
3) Lots of code was using INT and WORD, now wants DWORD, but then later it has to be LONGINT. Agghhhh!
LOads of DWORD(_cast,number) used
I hope to finish this tomorrow!!!!
I know exactly how you feel, Martin. It gets me the same way every single time..... >:(
:P ;D
-
And I have been using variants of this language for over 20 years. ::) ::) ::) ::)
The earliest pre Nantucket stuff was not great - used the Wordtech dbase 2 compiler.
Then the big move to Clipper S87
At the current job used Clipper 5.3 for years, still occasionally today. Also have some code in Alaska Xbase++ and our current product is in Visual Objects.
-
compilation errors can be resolved with some work but the generated run time code also may work differently..and need to be tested in detail.. :-/
-
double dutch to me lol
-
Sorry to say this, but sloppy coding to start with :'(
Or more accurately, your programmers haven't kept up with the software, as each revision of the development system would encourage more strict programming in an attempt to produce (hopefully) more robust code at the end. Older versions of the software allowed more sloppy, "quick and dirty" coding, as they were simpler systems. As high level languages move further and further away from low level, it makes more sense to build in safety.
I know how you feel - I have a couple of medium sized VB6 apps that run my brothers shops. VB6 is old school language - brilliant in its day for fast development, but way, way , way past its sell-by date. Actually out of support. All the other old apps I had rewritten or converted to new languages, but had entirely forgotten about these 2 until about a year ago when he wanted some mods done :-[
I ran an import into .NET - one had 1600 issues I needed to resolve (most fairly simple stuff), but the pos one, no way Jose, the importer could make head nor tail of some of my direct hardware control. *sigh*
So for now, dug out my old VB6 CDs, and been relearning that all year to make some mods he needs in before the Christmas rush (ie RIGHT NOW!), whilst at the time, gradually making the code more friendly to the .NET converter. I may still end up rewriting it from scratch anyway
-
Sorry to say this, but sloppy coding to start with :'(
Or more accurately, your programmers haven't kept up with the software, as each revision of the development system would encourage more strict programming in an attempt to produce (hopefully) more robust code at the end. Older versions of the software allowed more sloppy, "quick and dirty" coding, as they were simpler systems. As high level languages move further and further away from low level, it makes more sense to build in safety.
I know how you feel - I have a couple of medium sized VB6 apps that run my brothers shops. VB6 is old school language - brilliant in its day for fast development, but way, way , way past its sell-by date. Actually out of support. All the other old apps I had rewritten or converted to new languages, but had entirely forgotten about these 2 until about a year ago when he wanted some mods done :-[
I ran an import into .NET - one had 1600 issues I needed to resolve (most fairly simple stuff), but the pos one, no way Jose, the importer could make head nor tail of some of my direct hardware control. *sigh*
So for now, dug out my old VB6 CDs, and been relearning that all year to make some mods he needs in before the Christmas rush (ie RIGHT NOW!), whilst at the time, gradually making the code more friendly to the .NET converter. I may still end up rewriting it from scratch anyway
my sound daft, but there are still many vb6 projects in development ;D and still in use.. reason is obvious.. easy to learn and implement.. still supported by new operating systems .. can cooperate with all microsoft software.. and lots of ready code..
Hence, I expect minimum another 5 years for it to be discarded by programmers..
-
Sorry to say this, but sloppy coding to start with :'(
Or more accurately, your programmers haven't kept up with the software, as each revision of the development system would encourage more strict programming in an attempt to produce (hopefully) more robust code at the end. Older versions of the software allowed more sloppy, "quick and dirty" coding, as they were simpler systems. As high level languages move further and further away from low level, it makes more sense to build in safety.
I know how you feel - I have a couple of medium sized VB6 apps that run my brothers shops. VB6 is old school language - brilliant in its day for fast development, but way, way , way past its sell-by date. Actually out of support. All the other old apps I had rewritten or converted to new languages, but had entirely forgotten about these 2 until about a year ago when he wanted some mods done :-[
I ran an import into .NET - one had 1600 issues I needed to resolve (most fairly simple stuff), but the pos one, no way Jose, the importer could make head nor tail of some of my direct hardware control. *sigh*
So for now, dug out my old VB6 CDs, and been relearning that all year to make some mods he needs in before the Christmas rush (ie RIGHT NOW!), whilst at the time, gradually making the code more friendly to the .NET converter. I may still end up rewriting it from scratch anyway
my sound daft, but there are still many vb6 projects in development ;D and still in use.. reason is obvious.. easy to learn and implement.. still supported by new operating systems .. can cooperate with all microsoft software.. and lots of ready code..
Hence, I expect minimum another 5 years for it to be discarded by programmers..
I know reality, but no its out of support, it should be sent to the great s/w graveyard in the sky. For VB fans, VB.NET - particularly 2005 or 2008 is equally as easy to use, once you get your head around a slightly different way of working. Should really be used for all new projects (assuming you wish to stick with MS VB)
-
Sorry to say this, but sloppy coding to start with :'(
Or more accurately, your programmers haven't kept up with the software, as each revision of the development system would encourage more strict programming in an attempt to produce (hopefully) more robust code at the end. Older versions of the software allowed more sloppy, "quick and dirty" coding, as they were simpler systems. As high level languages move further and further away from low level, it makes more sense to build in safety.
I know how you feel - I have a couple of medium sized VB6 apps that run my brothers shops. VB6 is old school language - brilliant in its day for fast development, but way, way , way past its sell-by date. Actually out of support. All the other old apps I had rewritten or converted to new languages, but had entirely forgotten about these 2 until about a year ago when he wanted some mods done :-[
I ran an import into .NET - one had 1600 issues I needed to resolve (most fairly simple stuff), but the pos one, no way Jose, the importer could make head nor tail of some of my direct hardware control. *sigh*
So for now, dug out my old VB6 CDs, and been relearning that all year to make some mods he needs in before the Christmas rush (ie RIGHT NOW!), whilst at the time, gradually making the code more friendly to the .NET converter. I may still end up rewriting it from scratch anyway
my sound daft, but there are still many vb6 projects in development ;D and still in use.. reason is obvious.. easy to learn and implement.. still supported by new operating systems .. can cooperate with all microsoft software.. and lots of ready code..
Hence, I expect minimum another 5 years for it to be discarded by programmers..
I know reality, but no its out of support, it should be sent to the great s/w graveyard in the sky. For VB fans, VB.NET - particularly 2005 or 2008 is equally as easy to use, once you get your head around a slightly different way of working. Should really be used for all new projects (assuming you wish to stick with MS VB)
imho, for .net environment (2005,2008) c# or c++ not so complicated than new vb (anyway you have to use some object techniques) .. so if projects are going to be rewritten from scratch worth considering them also..(I do)
and I forgot to add, for .net environment as tools and techniques radically changed , development time must not be #1 priority as things need to be carefully planned (normal for the nature of object oriented design) or else you are using wrong tool..
-
Over 700 warnings in the order entry module alone ::) ::)
Must of them very simple like no return or return with no value.
It does look like they have strict typed quite a few library functions and classes - been checking the two versions.