> Message: 2 > Date: Tue, 04 Sep 2007 10:25:53 -0400 > From: Joe Yoder <[EMAIL PROTECTED]> > Subject: re: Unexplained behavior when attempting to write to a low > level file > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > On Tuesday, September 04, 2007 9:15 AM, Mike yearwood wrote: > >> Message: 9 > >> Date: Mon, 03 Sep 2007 17:42:54 -0400 > >> From: Joe Yoder <[EMAIL PROTECTED]> > >> Subject: re: Unexplained behavior when attempting to write to a low > >> level file > >> To: [EMAIL PROTECTED] > >> Message-ID: <[EMAIL PROTECTED]> > >> Content-Type: text/plain; charset="us-ascii" > >> > >> Sorry for bothering you all with my stupidity! The reason it wouldn't > >> work with the .PJX files is that they have a field named OutFile! When I > >> changed my use to m.OutFile all was well. > > > >Date: Tue, 4 Sep 2007 09:15:42 -0400 > >From: Mike yearwood > >To: [EMAIL PROTECTED] > >Subject: re: Unexplained behavior when attempting to write to a low level > >file > > > >If you always used m., you would not have tripped. :) > > > Thats what I always did in the DOS product. It seems styles have changed > and I don't see "m." in other peoples code anymore. I suspect that > prefixing names with "ln" for local numeric has taken it's place but have > not officially learned that this is the case. I'm trying to decide > whether to stay with what I know works or try to adopt current approaches > as I figure them out. Any advice?
Boy, do I ever! ;) I'm probably the biggest proponent of mdot. There's nothing outdated about it. Andy Kramek doesn't feel there's any value, but then I bet he's never wasted any time trying to debug an intermittent problem in someone else's code that was caused by not including mdots. See, naming conventions do not affect FoxPro directly, but mdot does! Since using it regularly, I've never suffered such a problem. I can fix any code by adding it without altering any existing naming convention, which proves naming conventions are irrelevant. Besides, in .Net they discourage hungarian notation! Basically it prevents the problem we saw here. It always improved performance, but it got even better: http://blogs.msdn.com/calvin_hsia/archive/2004/12/14/301282.aspx http://fox.wikis.com/wc.dll?Wiki~EssentialMDot~VFP Explicit is always better than implicit! Mike _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://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.
