Hi Dan,
That probably just answered the question I just posted on decoupling the
error handler so I can update it OUTSIDE of the app. I had put it into
a class so as to be able to have much more flexibility. For example,
I've got my CDO email routine working now, but I wanted to write
routines for MailSend/SendMail's method, plus the class allowed me to
compartmentalize a lot more as well. I've got methods for reporting the
error, logging it, uploading to the web database if possible, emailing
me (and working on more than one way to email it). The class allows me
to use properties moreso than having to pass parameters. It might seem
like splitting hairs, but I prefer the OOP approach moreso than the
procedural approach. I'm not a fan of passing lots of parms in this
case. I set my cTo, cFrom, cSubject, cTextBody and I then call
whichever email routine I've selected. Cleaner, imo.
Thanks,
--Mike
On 2014-08-03 11:10, Dan Covill wrote:
I guess it's the 'Old Programmer' syndrome showing, but it never
occurred to me to put the error routine in an object. Ours is just a
pretty big procedure in our utility lib (set procedure to). Doesn't
really matter where it is, so long as it's always available. It does
seem to me that _screen implies something dealing with display,
whereas the error routine is universal.
Yes, we were told back in the day that Separator was the lightest
class that still worked.
Dan
Date: Sun, 3 Aug 2014 00:07:09 -0400
From: [email protected]
To: [email protected]
Subject: Negative of attaching error handler object to _screen object?
I'm revamping my error reporting routine. Typically, I've had it in
my
public oUtils object. I was contemplating attaching it to the _screen
object instead. Can you think of any negatives to that? It's a very
lightweight class; I'm using a Separator class because I think there
was
something years ago that told me it was the lightest weight class
(which
could have methods, unlike the Empty class).
tia,
--Mike
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
