Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #2181
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: Vulcan build 208 |
| Date | 2011-10-06 17:15 +0200 |
| Organization | IC2 |
| Message-ID | <augr87p7a70faf30dc05atopt59eaisobc@4ax.com> (permalink) |
| References | <j653mq$85l$1@speranza.aioe.org> <3bel87p186igbgsmhgl7huklffdtt5keav@4ax.com> <j6it34$np8$1@speranza.aioe.org> <9ujq87ledb9elr4rqk0okbjdbcvuk482g8@4ax.com> <j6k6qo$kir$1@speranza.aioe.org> |
On Thu, 6 Oct 2011 07:27:12 -0500, "Willie Moore" <williem@wmconsulting.com> wrote: >Dick, > >I am not sure where you got the idea that you cant have a general error >handler. As Erik alread wrote, the application quits. That's the same as VO in the pre-errorhandling period....I have now, for example, in my general error handling a check if the error handling concerns a missing field. In that case, the error is logged and the log is e-mailed to me at the next startup but the user doesn't notice the problem until I notify them to run a conversion (or even do that for them if I have access). And I catch more situations: everything is logged but the user won't notice the error. If that's still possible in Vulcan without writing a TRY-CATCH-END TRY on every five lines of code, then this problem is solved. If not, then error handling would still be a major concern in Vulcan. >As far as the other points. I structure my apps so all of the projects in my >solution output to the same directory. Even without all the time and effort involved with this kind of structuring, I think I a right in my observation that change-save-compile-re-running a simple Vulcan app takes at least 8 seconds more than the same app in VO. Right? That still will cost me half an hour waiting time per programming day... Again: I see the pro's as well and my plan is to spend time again in Vulcan this month to see the nice things. But the shortcomings weigh heavily.... Dick
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-09-30 14:01 -0500
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-04 09:59 +0200
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-05 19:34 -0500
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 09:09 +0200
Re: Vulcan build 208 Johan Nel <johan.nel@xsinet.co.za> - 2011-10-06 00:35 -0700
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 11:33 +0200
Re: Vulcan build 208 Johan Nel <johan.nel@xsinet.co.za> - 2011-10-06 03:51 -0700
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 13:28 +0200
Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-06 15:28 +0200
Re: Vulcan build 208 "Ginny Caughey" <ginny.online@hotmail.com> - 2011-10-06 08:08 -0400
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 07:47 -0500
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 17:03 +0200
Re: Vulcan build 208 "Ginny Caughey" <ginny.online@hotmail.com> - 2011-10-07 08:27 -0400
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-07 08:51 -0500
Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-08 16:01 -0700
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-09 10:11 -0500
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 16:47 +0200
Re: Vulcan build 208 "Dirk (Belgium)" <dirk.dot.herijgers@pbprojects.dot.be> - 2011-10-06 07:36 +0000
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 11:48 +0200
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 07:27 -0500
Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-06 15:32 +0200
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 09:36 -0500
Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-06 19:33 +0200
Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 14:09 -0500
Re: Vulcan build 208 Massimo Bighelli <info@arcasistemi.it> - 2011-10-06 22:57 +0200
Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-06 23:39 +0200
Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-07 14:46 +0200
Re: Vulcan build 208 Massimo Bighelli <info@arcasistemi.it> - 2011-10-08 14:51 +0200
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 12:04 +0200
Re: Vulcan build 208 "Marc Verkade [Marti]" <marcatm@rti.nl> - 2011-10-07 15:52 +0200
Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-08 14:16 +0200
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 17:15 +0200
Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-06 19:07 +0200
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 12:03 +0200
Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-07 14:41 +0200
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 17:03 +0200
Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-07 17:26 +0200
Re: Vulcan build 208 Richard Wooters <Richard@rbj.com> - 2011-10-07 09:08 -0700
Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-06 16:13 -0700
Re: Vulcan build 208 "Jamal" <vodotnet_nospam@yahoo.com> - 2011-10-08 17:51 -0400
Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-08 15:42 -0700
Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-06 16:41 -0700
Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 11:58 +0200
Re: Vulcan build 208 info@softwareobjectives.com.au - 2011-10-04 02:47 -0700
Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-04 12:03 +0200
csiph-web