-->
Page 1 of 1

Documentation UPDATE Denote Potential Ghost Bug Causes

PostPosted: Sun Jan 29, 2017 2:04 am
by forlotto
What should be done is limitations should be denoted in the programming reference material so people are not so shocked by "GHOST BUGS" I think this is where a lot of these ghost issues come in is the lack of awareness of the limitations on the number of variables etc...

Variable limit = 70 (I think I recall this quoted somewhere)
Go Sub = 50 (I think without a return)
Lines of Code = 5000 (I think errr I wrote that in beginners guide.)
There was discussion of other limits to GUI Items etc... Maybe just for touchscreen I can't recall.
Timers also had a limitation of 1 I believe. Not sure.

Ghost bugs I believe are mostly limits at this point but they are undocumented this is a huge problem for anyone trying to write complex code like this or like easynet if we can document these limitations at least people could work around them. These things are very important to note I believe. I would have to go back and read everything problem is I think a lot of these things were given to me in chat and don't exist on the board so I kind of dropped the ball not taking notes and my memory is a bit foggy after coming back from my solar/wind project.
- See more at: viewtopic.php?f=41&t=13237&p=61693#p61693

Re: Documentation UPDATE Denote Potential Ghost Bug Causes

PostPosted: Sat Feb 04, 2017 7:04 pm
by flywire
I agree that these things need to be documented and it'll never be as nice as a compiler but the interpreter should handle programs exceeding limits gracefully.