Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #25586
| Subject | Re: Foxpro goto command and deleted records |
|---|---|
| From | Ed Leafe <ed@leafe.com> |
| Date | 2012-07-18 14:13 -0500 |
| References | <5005EDC0.6050608@stoneleaf.us> <8416AFAF-E201-4F89-B306-D89F920A00FE@leafe.com> <5006F0F7.8030004@stoneleaf.us> <485D3051-777B-49DA-8FD9-383F5807F827@leafe.com> <5006F91D.6030306@mrabarnett.plus.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2277.1342638823.4697.python-list@python.org> (permalink) |
On Jul 18, 2012, at 12:57 PM, MRAB wrote: >> #4 is probably the most Pythonic approach. The calling code can then decide how to react to attempting to access a deleted record. Even if you're accessing data stored in VFP tables, your module should be as Pythonic as possible. >> > I disagree. I think that if you can see it should be able to go to it. The use case was a deleted record with SET DELETED ON, which means you shouldn't "see" it. -- Ed Leafe
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Foxpro goto command and deleted records Ed Leafe <ed@leafe.com> - 2012-07-18 14:13 -0500
csiph-web