@rallard No problem, at one time we were all novices. When you get a compile error, scroll back the error log to the first error message and fix that. Often but not always the error msg will tell you what is wrong. In this case I was seeing error msgs that I have never seen before but by simply looking at the line (line # is in the error msg) I could see the problem. I have attached a picture of the first error. Notice that it points ^ to the 'thing' that is wrong, in this case the = assignment operator that should be the equality operator ==. BTW, a very common newbie error.
Did you manually copy the code, because it looks like in the case of the {} being [] that you are entering the code. Why not just use copy/paste to get the code and then do whatever you were planning on doing with it.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
@rallard It has nothing to do with the version of windows.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
@rallard Some error msgs can be very cryptic, but most are obvious. If you can't see the problem, look for another line of code similar to the one with an error and compare to see if you can spot the difference. It also might be helpful for learning to use ARDUINO IDE 2.0 or PlatformIO as they will highlight many errors before the compile step.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
Notice that it points ^ to the 'thing' that is wrong, in this case the = assignment operator that should be the equality operator ==. BTW, a very common newbie error.
Did you manually copy the code, because it looks like in the case of the {} being [] that you are entering the code. Why not just use copy/paste to get the code and then do whatever you were planning on doing with it.
I don't think that's supposed to be the equality symbol, more likely <= since it's a loop conditional. It wouldn't make sense as: for i starting at zero while i is equal to 256 ...
Anything seems possible when you don't know what you're talking about.
@will OMG, yes of course. The common error as I am sure you know is to mixup the = and ==. I failed to take the context into account. Hey, I been at this 63 years, the brain is leaking good data now, nowhere left to put it all. LOL BUT it does compile!!!
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
@will BTW, since this will take a while based on what we are seeing so far, how do we get the thread moved to a 'Help Wanted' section?
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
I would like to thank you for all your help. I have tried a few new projects using your advice and they worked out great! Thank you very much and thanks for working on what was going on with my compilier.
We use cookies on the DroneBot Workshop Forums to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
