I have a project that has been compiling fine. I just ran it but now GLBasic refuses to compile and run. It shows "precompiling..." then just stops. No errors, no nothing. I didn't make any changes since the last time I compiled and ran my project. Any idea what is going on? I have tried to reload the project, close the editor, etc. Nothing. This kind of thing is very frustrating.
So I load up the main source file into a text editor and lo and behold there are strange characters after some of the lines. It looks like a solid vertical block with a solid white circle in the middle (I'm wondering if this is some sort of folded code identifier or something?). I go about removing all of these then save it out as plain text. Then I load it back up in GLB and now that area of code it nackered up as a continuous line of code with no crlf and a solid block at the end of each command. So I remove these blocks and reformat my code. It will now run and compile but will now occasionally crash which it never did previous to this event.
Man oh man... what is up with that?
can you attach the project?
Try to unfold the SUB/FUNCTIONS.
In my codes, some SUB/FUNCTIONs are evils, and if they are folded, the compiler does not compile, just a blank debug window.
Send me these files, please. I'll have to fix that then.
Quote from: Kitty Hello on 2011-Mar-16
Send me these files, please. I'll have to fix that then.
are you talking to me?
Yes XD.
If you have a file with folded code that does not compile, please send it to me.
AlienMenace should sent the complete project too - it looks like some files are corrupt...
For what it's worth, I've had some strange behavior with folding code in general. I believe the part of my code that went screwy was folded. I like to fold all of my functions and have a blank line between them for code cleanliness reasons. Sometimes GLB will decide to unfold my functions on it's own and it also likes to remove that blank line I put in at random. I've had to add it back in fairly often. I've stopped using function folding for now, I love the idea but I don't trust it at the moment.
Quote from: AlienMenace on 2011-Mar-21
For what it's worth, I've had some strange behavior with folding code in general. I believe the part of my code that went screwy was folded. I like to fold all of my functions and have a blank line between them for code cleanliness reasons. Sometimes GLB will decide to unfold my functions on it's own and it also likes to remove that blank line I put in at random. I've had to add it back in fairly often. I've stopped using function folding for now, I love the idea but I don't trust it at the moment.
+1
It removes the separations, and it ended joining ENDSUB with the next sub, ENDSUBSUB name:
I am amazed no one else has this problem...
Most editors I have tried with code-folding has crached up on me when using folding. On the Atari it even caused bombings so you had to reset the machine. I never use code folding any more :-)
I loved the F9 fold/unfold in AMos Basic. BB3d/IDEal also had fold/unfold and it never crash (for me!)
Quote from: ampos on 2011-Mar-21
+1
It removes the separations, and it ended joining ENDSUB with the next sub, ENDSUBSUB name:
I am amazed no one else has this problem...
Yep, that very thing happens to me too. I was really into AMOS back in the day, spent hundreds of hours with my trusty old A500, DPaint and AMOS. :)
I started with EasyAMOS, then moved to AMOS Professional. I spent many a happy hour with those :)
Same thing just happened to me. However I unfolded and it's now compiling correctly for me again.
Quote from: ampos on 2011-Mar-21
I loved the F9 fold/unfold in AMos Basic. BB3d/IDEal also had fold/unfold and it never crash (for me!)
me too(amos pro)!
What I have coded so far in glbasic had no problem folding/unfolding.
Quote from: erico on 2011-May-11
Quote from: ampos on 2011-Mar-21
I loved the F9 fold/unfold in AMos Basic. BB3d/IDEal also had fold/unfold and it never crash (for me!)
me too(amos pro)!
What I have coded so far in glbasic had no problem folding/unfolding.
You have to have comments inside. I have not tested if the //coments on a single line had error, or just if you added the //comment after a sentence (as I do)