On Wed, Jul 18, 2012 at 8:40 AM, Grant Edwards wrote:
> On 2012-07-17, Ethan Furman wrote:
>
>> In Foxpro if you do a
>
> Foxpro?
http://en.wikipedia.org/wiki/Visual_FoxPro
--
http://mail.python.org/mailman/listinfo/python-list
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.
>>
>
On 18/07/2012 18:28, Ed Leafe wrote:
On Jul 18, 2012, at 12:16 PM, Ethan Furman wrote:
Your memory is good! I typed it in wrong.
Well, I was an MVP for Visual Foxpro for 10 years, so...
;-)
I see four other options:
0) don't move the pointer (listed for completeness)
1) g
On Jul 18, 2012, at 12:16 PM, Ethan Furman wrote:
> Your memory is good! I typed it in wrong.
Well, I was an MVP for Visual Foxpro for 10 years, so...
;-)
> I see four other options:
>
> 0) don't move the pointer (listed for completeness)
> 1) go to that record anyway
> 2) go
Ed Leafe wrote:
On Jul 17, 2012, at 5:57 PM, Ethan Furman wrote:
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't move the pointer (listed for completeness)
On Jul 17, 2012, at 5:57 PM, Ethan Furman wrote:
> In Foxpro if you do a
>
> GOTO 7
>
> with deleted off and record 7 is deleted, the record pointer doesn't
> move (at least in version 6).
>
> I don't like that.
>
> I see four other options:
>
> 0) don't move the pointer (listed for completen
On 2012-07-17, Ethan Furman wrote:
> In Foxpro if you do a
Foxpro?
--
Grant Edwards grant.b.edwardsYow! I am NOT a nut
at
gmail.com
--
http://mail.python.org/mailman/listinfo/p
MRAB wrote:
On 18/07/2012 03:19, Ethan Furman wrote:
MRAB wrote:
On 17/07/2012 23:57, Ethan Furman wrote:
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't m
On 18/07/2012 03:19, Ethan Furman wrote:
MRAB wrote:
On 17/07/2012 23:57, Ethan Furman wrote:
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't move the point
MRAB wrote:
On 17/07/2012 23:57, Ethan Furman wrote:
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't move the pointer (listed for completeness)
1) go to that
Ian Kelly wrote:
On Tue, Jul 17, 2012 at 4:57 PM, Ethan Furman wrote:
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't move the pointer (listed for completen
On 17/07/2012 23:57, Ethan Furman wrote:
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't move the pointer (listed for completeness)
1) go to that record anywa
On Tue, Jul 17, 2012 at 4:57 PM, Ethan Furman wrote:
> In Foxpro if you do a
>
> GOTO 7
>
> with deleted off and record 7 is deleted, the record pointer doesn't
> move (at least in version 6).
>
> I don't like that.
>
> I see four other options:
>
> 0) don't move the pointer (listed for completene
In Foxpro if you do a
GOTO 7
with deleted off and record 7 is deleted, the record pointer doesn't
move (at least in version 6).
I don't like that.
I see four other options:
0) don't move the pointer (listed for completeness)
1) go to that record anyway
2) go to the next undeleted record
3) go
14 matches
Mail list logo
