megaStrict

We have strict, superstrict...
I want Megastrict for Blitzmax!

- Blitzmax failing on wrong capitalisation of letter
- not enough comments for a certain script = wrong


:-P

Don't listen Mark, if you give him this the next thing he'll want is BMax dressed in leathers and holding a whip!

Megastrict indeed *boggle*

How about Ultrastrict while we're at it! Enforced naming conventions!

gigastrict?

Hmm. I use strict, what is the difference between strict and superstrict?

You get an electric shock through your keyboard, with superstrict.

Or how about Holystrict and get into the mode for programming in "heavenly" standards that requires the utmost God-approved perfection.....if you're into that kind of geeky stuff... :-P

With SuperStrict you must declare all of your variable types. Also, if your functions return something then that function needs to declare what variable type it returns. Example:

a:Int=Adder(1,2)
Print a
End

Function Adder:Int(a:Int,b:Int)
 Return a+b
End Function

With Strict if you do not specify the variable type Max will nominate undelcared variable as int.

Summary:
Think of Strict being the supply teacher and SuperStrict being the head master.

Replace strict with SuperStrict as default. There is no benefit to having both stricts, and superstrict is the only way to fly.

God, please, yes. I hate that...

I disagree - I use the regular Strict because it helps me keep track of my variables and not accidentally misspell one and end up assigning something to a non-existing one,t that's pretty much all I want out of it -- I would hate to be forced to jump through the additional hoops that SuperStrict imposes.

Those hoops are called "programming".

Whahaha

Sure. But nothing wrong with having the programming language simplyfying some things on your behalf, figuring out on its own what it should do?

Unless you using a HEX-editor to create your executables?

I'd rather use XtremeStrict. If you mispell a reserved word Bmax throws blood-thirsty badgers at you.

or reboot your computer without warning :)

"HEX-editor" pah, I use notepad and an extended ASCII charset. I used to just make beep noises into a microphone.

Why not make strict accept arguments?

strict( NO_GOTO | CASE_SENSITIVE | MUST_DECLARE_VARIABLE ) ' and so on...

everybody wins! \o/

edit: And it would be nice to be able to configure how the compiler behaves:

strict_warning( NO_GOTO ) ' It compiles but the compiler screams at you when you use goto.

deps: That idea is so unutterably bad that I don't really need to expand on it.

Having 2 levels of strict-ness is itself a gross hack and I hope that a more mature version of bmax will get rid of the idea entirely and enforce superstrict as the only way to use the language.

Agreed. It's not going to kill anyone here to learn to code properly.

I tend to agree. Provided Strict still remains optional.
Max is just as good as classic Blitz for thrashing out code in quick form. After which, you can go about your way dotting the I's and crossing the T's.

Here here. I myself feel like a more disciplined coder since using Max.

Really? I think it's a pretty good idea, since I want the compiler to be case sensitive, while some people doesn't. And sometimes I would like to use goto even if I'm using strict/superstrict. :)

SUPERSTRICT IZ 1337!!1!!!!

Well is not so bad. In some languages the coder can use a default 'strictness' or specify which rules you want to disable with preprocessor directives.

I don't know how an optional thing like that can be bad