Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ajf]

I think I'll make angl just do != 0 then.

You might consider adding a backwards-compatibility toggle that can be enabled on a per-file basis.  So, on the off chance that old code depends on GML's wonky behavior, it can still be made to work in angl.

Or you could implement the old GML behavior by default unless a script author specifies a flag that enables newer, more sensible angl behavior.  I'm basically borrowing the idea behind Javascript's "use strict".

I started off trying to copy actual implementation behaviour, but there's so much nonsensical undocumented stuff I'm going to make the parser and runtime quite strict. Unless you're using := and begin/end everywhere, things should work fine still, although some semicolons might be missing.

[MedO]

I'd aim for "easy to port code" rather than "strict backward compatibility", that way you keep the crud out of your base language without having to explicitly specify that you want sane behaviour.

[ajf]

I'd aim for "easy to port code" rather than "strict backward compatibility", that way you keep the crud out of your base language without having to explicitly specify that you want sane behaviour.

That's the idea. Well-written GML should mostly still work, at least in theory.

[ajf]

22:22 - ajf: protip
22:22 - ajf: directory_create("ServerPluginsCache");
22:22 - ajf: will
22:22 - ajf: SOMEHOW
22:22 - ajf: terminate the script
22:22 - ajf: but directory_create(working_directory + "\ServerPluginsCache");
22:22 - ajf: won't
22:22 - ajf: guess how I found this out
22:23 - PON: brute force
22:23 - ajf: yes
22:23 - ajf: I literally wrote JS that appended show_message("<line number>"); to the end of every single line

[Orpheon]

I still love the way game maker decides to just not call any create even if there's a room change, so if you create eg. a character at the wrong time, you get hoards of errors at completely different locations about uninitialised variables.

[Danikah]

I still love the way game maker decides to just not call any create even if there's a room change, so if you create eg. a character at the wrong time, you get hoards of errors at completely different locations about uninitialised variables.

Ouch, the memories.

[ajf]

[21:59] <wareya_> I like GM because it does exactly what it says unless it doesn't.

[Catman]

I love it when Gamemaker throws syntax errors at you when you use the auto-complete drop down suggestions... retyping it out fixes the false error...

[Dusty]

RoboDusty: I am not sure whether to slap the maker of GM
RoboDusty: Or kiss him.
RoboDusty: Say I have a script called game_init()
RoboDusty: I can do "example = game_init;" and then later do "script_execute(example);" and it would work as if I had typed "game_init();"

[Phantom Brave]

Working as intended!

[ajf]

RoboDusty: I am not sure whether to slap the maker of GM
RoboDusty: Or kiss him.
RoboDusty: Say I have a script called game_init()
RoboDusty: I can do "example = game_init;" and then later do "script_execute(example);" and it would work as if I had typed "game_init();"

That's how it's supposed to work.

[Phantom Brave]

He's complaining you can't go example(); or at least (example)();.

[Dusty]

No. I was just surprised that worked at all.
I was trying to figure out how to make a set of changeable weapons for a game, and thought of a way to do it.
I tried doing more complicated things like

Code: [Select]

execute_string("return "+scr_name+"();");but those didn't work, so I had to find something else.

[Phantom Brave]

Oh, I just kind of assumed you were used to how function pointers worked in C, which are like,
type func(args)
{
    ...
}

funcpointer = &func;

(*funcpointer)(args);

[ajf]

[18:36] <wareya> I like GML because it does exactly what it says unless it doesn't.