A category which contains compiler error message and the usual solution to the problem would be great. It could contain the soloution or just the Error message and a link to a post where the solution was given. This could save hours of searching!
Printable View
A category which contains compiler error message and the usual solution to the problem would be great. It could contain the soloution or just the Error message and a link to a post where the solution was given. This could save hours of searching!
This suggestions sounds good to me. Maybe a section in the WIKI?
Moderators, i need your feedback.
A wiki section/page sound good to me.
Agreed.
One of the first things I did as a junior mainframe programmer was to start a collection of error codes and solutions used. The thing grew into a large binder over 20 years.
OK, so under the WIKI entry in the front end CMS, I've added a section Compiler Error Codes.
If you'd like the description changed drop me a line.
Feel free to create articles in that section to document error codes and examples of correct syntax or whatever.
How does the WIKI work? Who adds the Warnings and/or error messages? How about the solutions or links? Thanks for adding. I know it will save me a lot of search time, once it is up and running.
Only moderators and contributors can make changes. We are working on content for this new section.
In the meantime if you have content to add post it here and it will be added. We like user input!!!
Users that wish to contribute can request contributor status by emailing or PM'ing me or a moderator.
We can elevate the user status to contributor and the user can create articles.
HOWEVER we will moderate and check articles before they go live to prevent abuse and spam
Here's one that took me a while to figure out:
Warning is:
"Warning Line 23: Command line overrides statement. (18F4550.BAS)"
Solution was:
Change the compiler from PBPW to PBPL by: View->Compile and Program Options-> Compiler->Select Check Box by "Use PBPL".
The "create article" button is missing.Quote:
Originally Posted by lester
http://www.picbasic.co.uk/forum/cont...64-error-codes
I started a wiki page in the new "Compiler Error Codes" section.
http://www.picbasic.co.uk/forum/cont...nd-Error-Codes
What was the code number?Quote:
Originally Posted by cc1984
Quote:
Originally Posted by mackrackit
No code number is returned. I get exactly what I typed in. What category do these "non-assigned" error codes fall into? It is definitely a fatal error, since it will not compile.
Interesting.Quote:
Originally Posted by cc1984
When I forget to use PBPL I get:
"....ERROR line 20: Bad data type."
That is with MCS. What are you using as a code editor/IDE?
Dave,
Does MPLAB give the same error messages than MCSP? Are there alternative IDEs?
I would think that error code numbers are IDE specific. Unless they all got together and came up with a standardized list, but that would surprise me greatly. It might be a good idea to separate the wiki by IDE product.
(I don't use MPLAB so can't comment on that)
Pic Basic Pro has codes of its own as MPASM does. The errors are saved to error files in your project directory. The IDE reads thos files.
As far as I know anyways.
I am using MicroCode Studio. What shipped on the PBP installation disk.Quote:
Originally Posted by mackrackit