moving from 2.7b to 2.8 - fixing compiler errors
in [Visual Objects]
|
Prev: Application Icon
Next: VO on a stick
From: Phil Turner on 16 Oct 2009 11:25 I posted a while ago but my post has gone, so here's the main part again. We finally got around to upgrading to 2.8 but have thousands of compilation errors. Is there a list anywhere of all the typical changes required? We are picking through these very slowly right now and a handful of global changes might make a big difference in our workload.
From: John Martens on 16 Oct 2009 13:31 Just by the return lines in a method you will get loads of errors. Going through them one by one is possibly just the best thing to do. Phil Turner schreef: > I posted a while ago but my post has gone, so here's the main part > again. > > > We finally got around to upgrading to 2.8 but have thousands of > compilation errors. > Is there a list anywhere of all the typical changes required? > We are picking through these very slowly right now and a handful of > global changes might make a big difference in our workload. >
From: Geoff Schaller on 16 Oct 2009 21:49 VO can turn off most of those warnings so to help, list the types involved, turn them all off and then turn them back on one by one, fixing as you go. Some of the warnings are important to fix and you should. Others are warnings on code style that are needed if you want to go to Vulcan. But even if you don't these, are good practice things to fix anyhow so I recommend you do them. And then if you do want to try Vulcan, you are better positioned to do so. Geoff "John Martens" <adsl672100(a)tiscali.nl> wrote in message news:4ad8ade7$0$28156$5fc3050(a)news.tiscali.nl: > Just by the return lines in a method you will get loads of errors. > Going through them one by one is possibly just the best thing to do. > > > Phil Turner schreef: > > > I posted a while ago but my post has gone, so here's the main part > > again. > > > > > > We finally got around to upgrading to 2.8 but have thousands of > > compilation errors. > > Is there a list anywhere of all the typical changes required? > > We are picking through these very slowly right now and a handful of > > global changes might make a big difference in our workload. > >
From: E®!k /!sser on 17 Oct 2009 04:22 > VO can turn off most of those warnings so to help, list the types > involved, turn them all off and then turn them back on one by one, fixing > as you go. > > Some of the warnings are important to fix and you should. > > Others are warnings on code style that are needed if you want to go to > Vulcan. But even if you don't these, are good practice things to fix > anyhow so I recommend you do them. And then if you do want to try Vulcan, > you are better positioned to do so. Yeh, we have been told a lot of rubish. Like we need return statements to make our code Vulcan ready. But like other .NET languages, Vulcan accepts methods without a return statement perfectly. . I guess this mandatory return statement is only there for the transporter. If this is the reason, it says a lot of the 'intelligence' of the transporter. Erik > > Geoff > > > > "John Martens" <adsl672100(a)tiscali.nl> wrote in message > news:4ad8ade7$0$28156$5fc3050(a)news.tiscali.nl: > >> Just by the return lines in a method you will get loads of errors. >> Going through them one by one is possibly just the best thing to do. >> >> >> Phil Turner schreef: >> >> > I posted a while ago but my post has gone, so here's the main part >> > again. >> > >> > >> > We finally got around to upgrading to 2.8 but have thousands of >> > compilation errors. >> > Is there a list anywhere of all the typical changes required? >> > We are picking through these very slowly right now and a handful of >> > global changes might make a big difference in our workload. >> > >
From: richard.townsendrose on 17 Oct 2009 06:19
Erik Why not do what's sensible ... Fix ALL Errors. Just because a compiler will tolerate sloppy programming is no reason to continue being sloppy ... its - [cannot find suitable words] ! Geoff ?? Richard |