[1.481] Advanced and Reg. Comps Same Error when nothing wrong.
Started by SNWLeader, Jan 16 2013 03:53 PM
8 replies to this topic
#1
Posted 16 January 2013 - 03:53 PM
Whenever I made my lock program it keeps telling me that 4 = expected. I know for sure that the program was typed correctly I know it is correct.
I put a space in it then It changes. So i try and delete the line of code, sure enough 4 = expected stays right in there. Can someone help me?
I put a space in it then It changes. So i try and delete the line of code, sure enough 4 = expected stays right in there. Can someone help me?
#2
Posted 16 January 2013 - 03:58 PM
SNWLeader, on 16 January 2013 - 03:53 PM, said:
Whenever I made my lock program it keeps telling me that 4 = expected. I know for sure that the program was typed correctly I know it is correct.
I put a space in it then It changes. So i try and delete the line of code, sure enough 4 = expected stays right in there. Can someone help me?
I put a space in it then It changes. So i try and delete the line of code, sure enough 4 = expected stays right in there. Can someone help me?
Secondly the error is indicating that it expecting an = sign... please post either all your code or at least lines 3-5 so we can see exactly whats wrong...
#3
Posted 16 January 2013 - 06:21 PM
Moved to Ask a Pro.
When you report something, just report it. No need to comment that you've reported it. I know this is at least the second time I've mentioned that to you.
When you report something, just report it. No need to comment that you've reported it. I know this is at least the second time I've mentioned that to you.
#4
Posted 16 January 2013 - 06:23 PM
Lyqyd, on 16 January 2013 - 06:21 PM, said:
Moved to Ask a Pro.
When you report something, just report it. No need to comment that you've reported it. I know this is at least the second time I've mentioned that to you.
When you report something, just report it. No need to comment that you've reported it. I know this is at least the second time I've mentioned that to you.
#5
Posted 17 January 2013 - 04:26 AM
TheOriginalBIT, on 16 January 2013 - 06:23 PM, said:
Lyqyd, on 16 January 2013 - 06:21 PM, said:
Moved to Ask a Pro.
When you report something, just report it. No need to comment that you've reported it. I know this is at least the second time I've mentioned that to you.
When you report something, just report it. No need to comment that you've reported it. I know this is at least the second time I've mentioned that to you.
I agree. I honestly think its no big deal.
On-Topic: We need to see your code.
#6
Posted 17 January 2013 - 08:13 AM
Eh, it can become a big deal to tell someone that you've reported their post, depending on the perceived reasons. It's always a pain to start some kind of feeble-minded drama about "messing with people's posts". And it can even be a pain to have a discussion of whether or not a program being developed belongs in Programs, Turtle Programs, or Ask a Pro (or Tutorials)--even if it's just a bore rather than a pain I'd rather avoid it.
And, hopefully most people are smart enough to figure out that the post being moved means that it was in the wrong forum.
So I guess the rule can be amended to "don't tell anyone that you're reporting a post, and don't point out any reasons that the post would be reported."
Anyway, the point on which we all agree is that we cannot confidently identify the error without seeing the code. Though a common cause is having forgotten the () on a function call in the previous line.
And, hopefully most people are smart enough to figure out that the post being moved means that it was in the wrong forum.
So I guess the rule can be amended to "don't tell anyone that you're reporting a post, and don't point out any reasons that the post would be reported."
Anyway, the point on which we all agree is that we cannot confidently identify the error without seeing the code. Though a common cause is having forgotten the () on a function call in the previous line.
#7
Posted 17 January 2013 - 12:49 PM
ChunLing, on 17 January 2013 - 08:13 AM, said:
Eh, it can become a big deal to tell someone that you've reported their post, depending on the perceived reasons. It's always a pain to start some kind of feeble-minded drama about "messing with people's posts". And it can even be a pain to have a discussion of whether or not a program being developed belongs in Programs, Turtle Programs, or Ask a Pro (or Tutorials)--even if it's just a bore rather than a pain I'd rather avoid it.
And, hopefully most people are smart enough to figure out that the post being moved means that it was in the wrong forum.
So I guess the rule can be amended to "don't tell anyone that you're reporting a post, and don't point out any reasons that the post would be reported."
And, hopefully most people are smart enough to figure out that the post being moved means that it was in the wrong forum.
So I guess the rule can be amended to "don't tell anyone that you're reporting a post, and don't point out any reasons that the post would be reported."
#8
Posted 17 January 2013 - 03:09 PM
No, just report it. If they post again in the wrong area, then we be sure to inform them of what they're doing wrong when we move/close the second topic. Most of the time, people figure out where their posts went the first time and manage to find them again, which usually leads to the realization that the area it moved to is the correct area for it to be posted in.
#9
Posted 17 January 2013 - 05:48 PM
It still shows up under their content search page, right? That's how I check to see if I've gotten replies to any of my posts.
16 user(s) are reading this topic
0 members, 16 guests, 0 anonymous users











