DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
Nesting error? But this works fine: Dimension test(1,1) test(1) = 'test' Paul Newton -----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Bill Anderson Sent: 06 June 2019 00:59 To: profoxtech@leafe.com Subject: [SUSPECTED SPAM] Funny bug
Sent by an external sender ------------------------------
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
Thank you for contacting ProFox technical support. Your email is important to us. Please read this entire message before replying, as our options have recently changed.
Due to unprecedented email volume, replying to your message may take longer than usual. Thank you for your patience. Please keep checking your emails, as email is replied-to in the order in which it is received, more or less.
In order to better assist you, we ask that you consider supplying the following information:
Just like "Jeopardy," you must form a question. If you are not asking a question, how can you expect an answer? Emails lacking the "?" character are not asking a question, and are moved to the bottom of the queue. Similarly, emails labeled "URGENT" or containing more than three exclamation points are also disregarded. If it wasn't important, why would you bother to ask? (Unless it's Friday afternoon and you're bored.)
What is it you were doing? The context of your situation almost always has some effect on what you witnessed. Were you at a computer? Was it turned on? Did you try turning it off and back on again? Was it a "Macintosh" computer? Was it running "Windows?" These answers may hold important clues.
What was it the computer did? The actual text on the screen is a lot more valuable than "It didn't work." If there is an error message, it has meaning and will help troubleshoot your problem. If the computer says, "I'm sorry, Dave, I can't do that," well, some problems may be beyond help.
What was it you expected the computer to do? If you told it to do something STUPID, and it did something stupid, well, duh. (99% of the time, when the computer does something stupid, it's in retaliation for something you did. Think about that, and review the point above, "What is it you were doing?")
What other clues can you supply? For example, "This was the first time I've started this computer" is different from "This application has been running fine for 30 years until I tried running it on WIn10-1903 last night." Or, "I just switched datasets to use the 4Gb of data from the customer." Or "I just changed one little thing." Or "Windows installed updates last night and the screen is all green."
What have you tried to resolve this issue? Did you search the error message on the web? Did you look up the problematic line of code in the manuals? The Hacker's Guide? Did you try to reproduce the error? Did you turn off the machine and turn it on again? Did you pack the tables and recreate the indexes? Can you reproduce the error in a few lines of code?
Thank you for using ProFox technical support. We appreciate that you have many choices in FoxPro support, and greatly value your loyalty. Please ensure that your tray is stowed, your seat is in its upright position and note that the nearest exit may be behind you.
- finis
"Boom!" Nice catch, Bill!
This made my day. Thanks, Ted!
You put the "funny" back in the bug! :)
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Thursday, June 06, 2019 8:07 AM To: profoxtech@leafe.com Subject: Re: Funny bug
On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
Thank you for contacting ProFox technical support. Your email is important to us. Please read this entire message before replying, as our options have recently changed.
Due to unprecedented email volume, replying to your message may take longer than usual. Thank you for your patience. Please keep checking your emails, as email is replied-to in the order in which it is received, more or less.
In order to better assist you, we ask that you consider supplying the following information:
Just like "Jeopardy," you must form a question. If you are not asking a question, how can you expect an answer? Emails lacking the "?" character are not asking a question, and are moved to the bottom of the queue. Similarly, emails labeled "URGENT" or containing more than three exclamation points are also disregarded. If it wasn't important, why would you bother to ask? (Unless it's Friday afternoon and you're bored.)
What is it you were doing? The context of your situation almost always has some effect on what you witnessed. Were you at a computer? Was it turned on? Did you try turning it off and back on again? Was it a "Macintosh" computer? Was it running "Windows?" These answers may hold important clues.
What was it the computer did? The actual text on the screen is a lot more valuable than "It didn't work." If there is an error message, it has meaning and will help troubleshoot your problem. If the computer says, "I'm sorry, Dave, I can't do that," well, some problems may be beyond help.
What was it you expected the computer to do? If you told it to do something STUPID, and it did something stupid, well, duh. (99% of the time, when the computer does something stupid, it's in retaliation for something you did. Think about that, and review the point above, "What is it you were doing?")
What other clues can you supply? For example, "This was the first time I've started this computer" is different from "This application has been running fine for 30 years until I tried running it on WIn10-1903 last night." Or, "I just switched datasets to use the 4Gb of data from the customer." Or "I just changed one little thing." Or "Windows installed updates last night and the screen is all green."
What have you tried to resolve this issue? Did you search the error message on the web? Did you look up the problematic line of code in the manuals? The Hacker's Guide? Did you try to reproduce the error? Did you turn off the machine and turn it on again? Did you pack the tables and recreate the indexes? Can you reproduce the error in a few lines of code?
Thank you for using ProFox technical support. We appreciate that you have many choices in FoxPro support, and greatly value your loyalty. Please ensure that your tray is stowed, your seat is in its upright position and note that the nearest exit may be behind you.
- finis
"Boom!" Nice catch, Bill!
That's funny!
On Thu, Jun 6, 2019 at 8:06 AM Ted Roche tedroche@gmail.com wrote:
On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
Thank you for contacting ProFox technical support. Your email is important to us. Please read this entire message before replying, as our options have recently changed.
Due to unprecedented email volume, replying to your message may take longer than usual. Thank you for your patience. Please keep checking your emails, as email is replied-to in the order in which it is received, more or less.
In order to better assist you, we ask that you consider supplying the following information:
Just like "Jeopardy," you must form a question. If you are not asking a question, how can you expect an answer? Emails lacking the "?" character are not asking a question, and are moved to the bottom of the queue. Similarly, emails labeled "URGENT" or containing more than three exclamation points are also disregarded. If it wasn't important, why would you bother to ask? (Unless it's Friday afternoon and you're bored.)
What is it you were doing? The context of your situation almost always has some effect on what you witnessed. Were you at a computer? Was it turned on? Did you try turning it off and back on again? Was it a "Macintosh" computer? Was it running "Windows?" These answers may hold important clues.
What was it the computer did? The actual text on the screen is a lot more valuable than "It didn't work." If there is an error message, it has meaning and will help troubleshoot your problem. If the computer says, "I'm sorry, Dave, I can't do that," well, some problems may be beyond help.
What was it you expected the computer to do? If you told it to do something STUPID, and it did something stupid, well, duh. (99% of the time, when the computer does something stupid, it's in retaliation for something you did. Think about that, and review the point above, "What is it you were doing?")
What other clues can you supply? For example, "This was the first time I've started this computer" is different from "This application has been running fine for 30 years until I tried running it on WIn10-1903 last night." Or, "I just switched datasets to use the 4Gb of data from the customer." Or "I just changed one little thing." Or "Windows installed updates last night and the screen is all green."
What have you tried to resolve this issue? Did you search the error message on the web? Did you look up the problematic line of code in the manuals? The Hacker's Guide? Did you try to reproduce the error? Did you turn off the machine and turn it on again? Did you pack the tables and recreate the indexes? Can you reproduce the error in a few lines of code?
Thank you for using ProFox technical support. We appreciate that you have many choices in FoxPro support, and greatly value your loyalty. Please ensure that your tray is stowed, your seat is in its upright position and note that the nearest exit may be behind you.
- finis
"Boom!" Nice catch, Bill!
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
Roflmao!
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Ted Roche Sent: Thursday, June 6, 2019 9:07 AM To: profoxtech@leafe.com Subject: Re: Funny bug
On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
Thank you for contacting ProFox technical support. Your email is important to us. Please read this entire message before replying, as our options have recently changed. ... Thank you for using ProFox technical support. We appreciate that you have many choices in FoxPro support, and greatly value your loyalty. Please ensure that your tray is stowed, your seat is in its upright position and note that the nearest exit may be behind you.
- finis
"Boom!" Nice catch, Bill!
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
+1
John Weller 01380 723235 07976 393631
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Richard Kaye Sent: 06 June 2019 17:15 To: profoxtech@leafe.com Subject: RE: Funny bug
Roflmao!
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Ted Roche Sent: Thursday, June 6, 2019 9:07 AM To: profoxtech@leafe.com Subject: Re: Funny bug
On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
Thank you for contacting ProFox technical support. Your email is important to us. Please read this entire message before replying, as our options have recently changed. ... Thank you for using ProFox technical support. We appreciate that you have many choices in FoxPro support, and greatly value your loyalty. Please ensure that your tray is stowed, your seat is in its upright position and note that the nearest exit may be behind you.
- finis
"Boom!" Nice catch, Bill!
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]
From the command window, I get "Nesting Error" which is the same message
I'd get if I just typed,
NEXT
Which is funny, because a line like,
FOR x = 1 to n
returns "Statement is not allowed in interactive mode."
Same in a junk program. FoxPro 09.00.0000.7423
On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
That's a compelling argument for the use of mdot *whenever* possible!
m.Next(1) = .F. && no-boom!
On Thu, Jun 6, 2019 at 12:59 AM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
Well, it is still not advisable to use reserved/keywords in any programming language...
for for = 1 to 10 next = next + 1 do = do * 3 if next < 5 end = end - 1 end if next
On 2019/06/06 15:50, António Tavares Lopes wrote:
That's a compelling argument for the use of mdot *whenever* possible!
m.Next(1) = .F. && no-boom!
On Thu, Jun 6, 2019 at 12:59 AM Bill Anderson billand88@gmail.com wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
The mdot is almost the single piece of functionality in VFP that acts like a namespacing container / insulator. If I had any advice to give, it should be to use it at full discretion.
for m.for = 1 to 10 m.next = m.next + 1 m.do = m.do * 3 if m.next < 5 m.end = m.end - 1 end if next
On Thu, Jun 6, 2019 at 3:34 PM Johan Nel johan.nel@xsinet.co.za wrote:
Well, it is still not advisable to use reserved/keywords in any programming language...
for for = 1 to 10 next = next + 1 do = do * 3 if next < 5 end = end - 1 end if next
On 2019/06/06 15:50, António Tavares Lopes wrote:
That's a compelling argument for the use of mdot *whenever* possible!
m.Next(1) = .F. && no-boom!
On Thu, Jun 6, 2019 at 12:59 AM Bill Anderson billand88@gmail.com
wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
+1 for mdot, except on assigned variables where there’s no ambiguity:
end = m.end + 1
Thierry Nivelet http://foxincloud.com/ Give your VFP app a second life in your cloud
Le 6 juin 2019 à 16:56, António Tavares Lopes atlopes@gmail.com a écrit :
The mdot is almost the single piece of functionality in VFP that acts like a namespacing container / insulator. If I had any advice to give, it should be to use it at full discretion.
for m.for = 1 to 10 m.next = m.next + 1 m.do = m.do * 3 if m.next < 5 m.end = m.end - 1 end if next
On Thu, Jun 6, 2019 at 3:34 PM Johan Nel johan.nel@xsinet.co.za wrote:
Well, it is still not advisable to use reserved/keywords in any programming language...
for for = 1 to 10 next = next + 1 do = do * 3 if next < 5 end = end - 1 end if next
On 2019/06/06 15:50, António Tavares Lopes wrote: That's a compelling argument for the use of mdot *whenever* possible!
m.Next(1) = .F. && no-boom!
On Thu, Jun 6, 2019 at 12:59 AM Bill Anderson billand88@gmail.com
wrote:
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
On Thu, Jun 6, 2019 at 9:50 AM António Tavares Lopes atlopes@gmail.com wrote:
That's a compelling argument for the use of mdot *whenever* possible!
m.Next(1) = .F. && no-boom!
Excellent point!
Cool thing! But:
STORE .F. TO Next(1)
&& no kaboom :)
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Bill Anderson Gesendet: Donnerstag, 6. Juni 2019 01:59 An: ProFox Email List profox@leafe.com Betreff: Funny bug
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
On Thu, Jun 6, 2019 at 4:17 PM juergen@wondzinski.de wrote:
Cool thing! But:
STORE .F. TO Next(1)
&& no kaboom :)
Yes, indeed. The language parser has no trouble interpreting what you mean.
When NEXT is the first non-white-space characters on the line, FoxPro goes off looking for the FOR clause and breaks.
This made me think that we should hold a contest on this support network to create the most convoluted way to do something simple like assign a particular value to a variable. A Rube Goldberg Programming challenge. I believe with the sense of humor the members here have, it would be an absolute hoot to see how complicated we could make a simple variable assignment and extra points for obfuscating the code as well.
Then again, I've been so busy lately, I fell off the stats two months in a row. A blessing for sure, but still...
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of juergen@wondzinski.de Sent: Thursday, June 06, 2019 3:17 PM To: profoxtech@leafe.com Subject: AW: Funny bug
Cool thing! But:
STORE .F. TO Next(1)
&& no kaboom :)
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Bill Anderson Gesendet: Donnerstag, 6. Juni 2019 01:59 An: ProFox Email List profox@leafe.com Betreff: Funny bug
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
At 15:16 2019-06-06, "Paul H. Tarver" paul@tpcqpc.com wrote:
This made me think that we should hold a contest on this support network to create the most convoluted way to do something simple like assign a particular value to a variable. A Rube Goldberg Programming challenge. I believe with the sense of humor the members here have, it would be an absolute hoot to see how complicated we could make a simple variable assignment and extra points for obfuscating the code as well.
I had an idea once of having a contest for the most convoluted way to exit a form normally. You could have validations having to be performed in a certain order (remarkably different from Z-order, of course) and other such nasties. However, the only reason I am ever on the Dark Side is for the odd cookie so I demurred.
Then again, I've been so busy lately, I fell off the stats two months in a row. A blessing for sure, but still...
I hope that means dollarful (as opposed to doleful).
[snip]
Sincerely,
Gene Wirchenko
https://www.ioccc.org/ , anybody? :-)
On Thu, Jun 6, 2019 at 6:17 PM Paul H. Tarver paul@tpcqpc.com wrote:
This made me think that we should hold a contest on this support network to create the most convoluted way to do something simple like assign a particular value to a variable. A Rube Goldberg Programming challenge. I believe with the sense of humor the members here have, it would be an absolute hoot to see how complicated we could make a simple variable assignment and extra points for obfuscating the code as well.
Then again, I've been so busy lately, I fell off the stats two months in a row. A blessing for sure, but still...
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of juergen@wondzinski.de Sent: Thursday, June 06, 2019 3:17 PM To: profoxtech@leafe.com Subject: AW: Funny bug
Cool thing! But:
STORE .F. TO Next(1)
&& no kaboom :)
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Bill Anderson Gesendet: Donnerstag, 6. Juni 2019 01:59 An: ProFox Email List profox@leafe.com Betreff: Funny bug
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
Cool, but not Foxpro!
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Garrett Fitzgerald Sent: Friday, June 07, 2019 1:38 PM To: profoxtech@leafe.com Subject: Re: Funny bug
https://www.ioccc.org/ , anybody? :-)
On Thu, Jun 6, 2019 at 6:17 PM Paul H. Tarver paul@tpcqpc.com wrote:
This made me think that we should hold a contest on this support network to create the most convoluted way to do something simple like assign a particular value to a variable. A Rube Goldberg Programming challenge. I believe with the sense of humor the members here have, it would be an absolute hoot to see how complicated we could make a simple variable assignment and extra points for obfuscating the code as well.
Then again, I've been so busy lately, I fell off the stats two months in a row. A blessing for sure, but still...
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of juergen@wondzinski.de Sent: Thursday, June 06, 2019 3:17 PM To: profoxtech@leafe.com Subject: AW: Funny bug
Cool thing! But:
STORE .F. TO Next(1)
&& no kaboom :)
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Bill Anderson Gesendet: Donnerstag, 6. Juni 2019 01:59 An: ProFox Email List profox@leafe.com Betreff: Funny bug
DECLARE Next(1, 1) Next(1) = .F. && Boom!
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
-
Alan Bourke -
António Tavares Lopes -
Bill Anderson -
Eric Selje -
Garrett Fitzgerald -
Gene Wirchenko -
Johan Nel -
John Weller -
juergen＠wondzinski.de -
Paul H. Tarver -
Paul Newton -
Richard Kaye -
Ted Roche -
Thierry Nivelet