That's weird. I 've been using lowerdash for a long time and I haven't got that issue. Remember that you must put both lowerdash and lowerdash_c on your development project. Could you post the code of the file that load the framework? Maybe there is the problem.I actually do *not* have it loading both 'lowerdash' & 'lowerdash_c'. In which slots should I put each? Both files in the comments at the top are telling me to put them in slot 2. Which actually goes in 1? Also, should I load them both up through code such as how I did with 'lowerdash_c' as shown in the picture on Miiverse or do I need to do it manually for one? Thanks for the help raimondz!
Also, you should use function instead of labels.Labels are actually a teeny bit faster. Lowerdash has module labels (@@), but I don't use them enough to know if they have overhead. They create a bunch of fun GOTO jumps when you first do main.
Also good to know regarding the labels. I'll revert all the functions I can back to labels again >.>I didn't see the code in question, so I'm just adding general advice. Labels are faster, but Lowerdash will require functions for instance methods. I also often write functions just to keep the scope (list of variable definitions) clean. It's really a matter of personal taste and how fast that piece of code has to run. I'm excited to have another
They were all coming off of the main loop, a basic framework for the game. It lists out stuff like an input poller, renderer, scene management, all currently doing nothing yet. If subroutines are faster, I will use that for these as I always have. I will use functions when I have need to return variables, use more than once per frame or just to keep organized because keeping scope is keeping tidy. I would like to create a controllable object by tomorrow, which should be useful for a game idea I've had that could make use of OOP. Hopefully I'll break Lowerdash real good for you, haha. What kind of info would you like me to give in the case I do? I assume it keeps no error log?Also good to know regarding the labels. I'll revert all the functions I can back to labels again >.>I didn't see the code in question, so I'm just adding general advice. Labels are faster, but Lowerdash will require functions for instance methods. I also often write functions just to keep the scope (list of variable definitions) clean. It's really a matter of personal taste and how fast that piece of code has to run. I'm excited to have anotherbug finderuser! I've been way too busy to really sit down and break 0.5.
I have a new question now concerning prototypes. It would appear I could use one to make as a template for another class, so I take it I could do something like make a prototype loaded with information such as animations and hitboxes then use that prototype within a module that has information such as what commands use which animations, AI & other information?Yep! In my game library, I use a prototype's constructor (and its prototype's constructor) to setup the sprite and hitbox and get a Physics management number.
I would love for a practical example, I see the BALL demo uses PROTO (named "INBOUNDS"), however I don't see it to being any benefit or what that is for. Thanks in advance for any help!This is a much better example. I might try to adapt it to something simple. (The problem is a ball demo can't have THAT many animations) The inbounds mixin could be used with other modules as well. A bullet can check if its inbounds. I admit, its a contrived example trying to emulate what happens when, e.g, you have a physics library handling that part.
I read over it again and I must have missed the INBOUNDS module. Having seen it, I think I understand it's implementation now. I use PROTO within or right after declaring a MODULE and then it inherits the properties of another MODULE by the same name as a prototype. In other words, I think it's all understood now & I'll be sorting out a bunch of code!I have a new question now concerning prototypes. It would appear I could use one to make as a template for another class, so I take it I could do something like make a prototype loaded with information such as animations and hitboxes then use that prototype within a module that has information such as what commands use which animations, AI & other information?Yep! In my game library, I use a prototype's constructor (and its prototype's constructor) to setup the sprite and hitbox and get a Physics management number.I would love for a practical example, I see the BALL demo uses PROTO (named "INBOUNDS"), however I don't see it to being any benefit or what that is for. Thanks in advance for any help!This is a much better example. I might try to adapt it to something simple. (The problem is a ball demo can't have THAT many animations) The inbounds mixin could be used with other modules as well. A bullet can check if its inbounds. I admit, its a contrived example trying to emulate what happens when, e.g, you have a physics library handling that part.
I use PROTO within or right after declaring a MODULE and then it inherits the properties of another MODULE by the same name as a prototype. In other words, I think it's all understood now & I'll be sorting out a bunch of code!Yep! One caveat- It's one command now (0.5):
MODULE name [PROTO name]where [PROTO name] is optional. It is needed IMMEDIATELY after MODULE, and I think it was misleading to have the option of putting it in the wrong place. Only downside is that, that one line can get pretty long. EDIT: I fixed that example
Great! Corrected it in my own code. Yes, I see you updating at least weekly these days. I have a plan for a game that would use objects, but I have made no calls yet as I've got about 600 lines of code I'm using as a framework for the rest of the game right now. I'm just happy it compiles, but looking forward to calling some of my objects when I think they are done. Oh! That does remind me I have had trouble running it 'scripted' through LowerDash though (as in, not compiled). 'head' gives back a syntax error, but it works when I compile, so I've just been doing that. Secondly, how do I run the compiled program? It runs fine after compiling, but I can't seem to run it on it's own. It starts with 'END', after all... so what do I do with it? I must be missing something. Thanks for all your help & extra thanks for all the updated documentation! It's been really helpful, because of it I should have some an 'entity' prototype & other objects ready to test soon. Looking forward to 0.5!I use PROTO within or right after declaring a MODULE and then it inherits the properties of another MODULE by the same name as a prototype. In other words, I think it's all understood now & I'll be sorting out a bunch of code!Yep! One caveat- It's one command now (0.5):MODULE name [PROTO name]where [PROTO name] is optional. It is needed IMMEDIATELY after MODULE, and I think it was misleading to have the option of putting it in the wrong place. Only downside is that, that one line can get pretty long. EDIT: I fixed that example
Oh! That does remind me I have had trouble running it 'scripted' through LowerDash though (as in, not compiled). 'head' gives back a syntax error, but it works when I compile, so I've just been doing that. Secondly, how do I run the compiled program? It runs fine after compiling, but I can't seem to run it on it's own. It starts with 'END', after all... so what do I do with it? I must be missing something.I'm curious what the syntax error is. You end the head with hend. To load the compiled file, you still have to have a program with a MAIN section. The compiled code can be loaded into slot 3 instead of loading LOWERDASH_C in slot 2 and having a HEAD section. It is a file containing the Lowerdash runtime as well as your compiled code. It is possible to copy and paste your MAIN section to the top of the compiled file just before that END you noticed. (Slot 3 will still be hard coded... part of why theres no tool for this yet)
Yes, I switch between the compile and hend commands by commenting out the opposite. After 'main'? First it's a label, then ACLS. It prints a message notifying user of startup and it makes several global declarations then goes into the main loop from there. I have no clue what could be causing the error either, unfortunately. Edit: Oooh! I see what you're saying. I will try adding the 'main' command to that compiled file then.Oh! That does remind me I have had trouble running it 'scripted' through LowerDash though (as in, not compiled). 'head' gives back a syntax error, but it works when I compile, so I've just been doing that. Secondly, how do I run the compiled program? It runs fine after compiling, but I can't seem to run it on it's own. It starts with 'END', after all... so what do I do with it? I must be missing something.I'm curious what the syntax error is. You end the head with hend. To load the compiled file, you still have to have a program with a MAIN section. The compiled code can be loaded into slot 3 instead of loading LOWERDASH_C in slot 2 and having a HEAD section. It is a file containing the Lowerdash runtime as well as your compiled code. It is possible to copy and paste your MAIN section to the top of the compiled file just before that END you noticed. (Slot 3 will still be hard coded... part of why theres no tool for this yet)
I have no clue what could be causing the error either, unfortunately.What does the error say?
makes several global declarationsI don't know if you're aware, but SmileBasic doesn't have true globals; top-level variables will be bound to the slot. So you can only retrieve them in other slots with VAR("1:myGlobal"). I've been dropping my "globals" in a separate imported file, which makes them available in the same slot as module code.
There is no error feedback, unfortunately. It just says "[GAME]OK", like it performed an END & triggered the program ending when 'main' is used. Also I finally got around to trying out objects. It simply cannot find them. I have them saved under "_OBJDATA" and have set that to be imported. It cannot see my "Entity" MODULE. The Lowerdash error: "No module named Entity", however that is not true, it is in that imported _OBJDATA file. Thanks for all the help as usual!I have no clue what could be causing the error either, unfortunately.What does the error say?After 'main'? First it's a label, then ACLS.MAIN runs any loose code that is in the modules and sets up the variable declarations. ACLS should come before MAIN
