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 --- _______________________________________________ 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.
