Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Profile
Locker
Play ListsFLYINGJESTER'S PROFILE
Close
I am the Jester.
I make games using JavaScript, C, C++, Mercury, Java, Assembly (amd64 and UltraSparc) and Python. I used to use Sphere a lot, but I'm more into C/C++ and Mercury nowadays. I still use JavaScript and embed it sometimes, and I usually use Python for build systems and system management.
I wrote TurboSphere, which is a recreation of the Sphere Game Engine with a number of major improvements. I'm not really working on it anymore.
I'm surely going to finish making a game someday. I mean, sooner or later, it's bound to happen. Right?
I make games using JavaScript, C, C++, Mercury, Java, Assembly (amd64 and UltraSparc) and Python. I used to use Sphere a lot, but I'm more into C/C++ and Mercury nowadays. I still use JavaScript and embed it sometimes, and I usually use Python for build systems and system management.
I wrote TurboSphere, which is a recreation of the Sphere Game Engine with a number of major improvements. I'm not really working on it anymore.
I'm surely going to finish making a game someday. I mean, sooner or later, it's bound to happen. Right?
Search
Filter
All
Game Pages
No-RM Event
I started on my game. I'm going to try to make a strategy game in ANSI C...without using any loops!.
I used to work on a lot of strategy games. This reminds me how much fun it is!
I used to work on a lot of strategy games. This reminds me how much fun it is!
What are you thinking about right now?
When is someone going to make Llama Simulator?
Oh yeah, Maxis is out of business. They were the only ones I could count on for such a thing.
Oh yeah, Maxis is out of business. They were the only ones I could count on for such a thing.
I have to chuckle a bit everyime someone mistakes my 'made-in-editor' maps for parallax fests.
What are you thinking about right now?
I'm wondering why I can't get mercury-cell batteries. I really want to put mercury-cell CR2032s in my Sega Saturn and my Dreamcast's VMUs (or CR2016s, I'll pad them out with dimes).
I think it will just feel more satisfying to play a game knowing my saves are backed up using the power of mercury.
I think it will just feel more satisfying to play a game knowing my saves are backed up using the power of mercury.
[Poll] Is Harder Better Faster Stronger the best song ever?
I just realized what variable hoisting is. And I feel like a noob for it taking this long.
Sort of. It's anytime the compiler changes 'where' a variable exists. Either by 'hoisting' it up to the start of the scope (as in C or C++, or really any compiled language), or 'hoisting' it out of the scope it was declared in (as in JavaScript).
I just realized what variable hoisting is. And I feel like a noob for it taking this long.
Variable hoisting is changing the scope of a variable's lifetime.
In ANSI C (aka, this code will work absolutely everywhere), you need to declare variables at the start of a scope. After the start of a scope, you have as many variable declarations as you want. But once you have even one thing that isn't a variable declaration, you can't have any more variable declarations in that scope.
The reason is that all variables are held on the stack, and weaker compilers had a super hard time with growing the stack in the middle a scope (that's kind of what scope is, an area where the stack is larger than before).
In modern days, this is fine:
But the variable is 'hoisted' to the start of the scope. To the compiler, this is the same thing as the first function. This is because the compiler will need to grow the stack to hold the variable, and so it grows it at the start of the scope rather than in the middle.
In JavaScript (where I heard the term originally), it goes even further. When you declare something with 'var' (as opposed to the new term, 'let'), the variable is 'hoisted' to function scope. You can use it outside the scope you declared it in, as long as you use it in the same function, and after you declared it.
I've written compilers and interpreters before. I feel silly for only figuring this out now :P
In ANSI C (aka, this code will work absolutely everywhere), you need to declare variables at the start of a scope. After the start of a scope, you have as many variable declarations as you want. But once you have even one thing that isn't a variable declaration, you can't have any more variable declarations in that scope.
/* ANSI C */
int someFunc(int x){
int y;
x = x*2;
/* I couldn't declare y here because there is a statement before it */
y = x;
return y;
}
The reason is that all variables are held on the stack, and weaker compilers had a super hard time with growing the stack in the middle a scope (that's kind of what scope is, an area where the stack is larger than before).
In modern days, this is fine:
/* C99 */
int someFunc(int x){
x = x*2;
/* Who cares? I didn't use it before I declared it. */
int y = x;
return y;
}
But the variable is 'hoisted' to the start of the scope. To the compiler, this is the same thing as the first function. This is because the compiler will need to grow the stack to hold the variable, and so it grows it at the start of the scope rather than in the middle.
In JavaScript (where I heard the term originally), it goes even further. When you declare something with 'var' (as opposed to the new term, 'let'), the variable is 'hoisted' to function scope. You can use it outside the scope you declared it in, as long as you use it in the same function, and after you declared it.
/* JavaScript */
function someFunc(){
{
var x = 23;
}
return x; // This is fine. x was hoisted out of its scope by 'var'.
}
I've written compilers and interpreters before. I feel silly for only figuring this out now :P
No-RM Event
I'm excited for this! Then again, I only join events here when they are for any engine, just because I never use RPGMaker.
Then I'll just have to really turn up the strange-ness, engine-wise. Maybe I'll finally commit to making a game in a proper functional language, like Mercury or Haskell.
Then I'll just have to really turn up the strange-ness, engine-wise. Maybe I'll finally commit to making a game in a proper functional language, like Mercury or Haskell.
Games - Tester
Games - Other
