I dont get it either:
Issues:
1. 'Code to generate a type list causes bloat'. Solution: Allow an 'autolist' declaration in each type, that creates said list behind the scenes.
2. Docs still need improvement. This may be responsible for the perceived difficulty of BlitzMax?
3. Lack of built in 3D. It's in the pipe-works. Not a lot we can do in the meantime.
4. Poor built in IDE.
1. Which not only makes it more powerful, but code can also be unbloated with things like methods etc.
2. Totally agree
3. s mark said recently, Max3D is underway in the form of a completely spanking new "B3D-like" engine lib.
4. Agreed(was b3d's much better?), but for windows theres loads of alternatives.
Non issues:
1. 'I don't like OOP'.
2. 'It isn't cute... it isn't named Blitz3D2'.
1 Dont invoke it then. Just use it as you would blitz3d.
2. Lol (someone actually said that??) you could always rename the exe & change the logo!.
BM superiorities:
1. Cross platform
2. Optimising compiler
3. OOP (ish)
4. Multiple lists per type (this one can be a positive or a negative)
5. Garbage collection is nice (when it's not causing headaches)
6. 'Out of the box' support for including media in the binary
7. '2D in 3D' out of the box... rotatey, alpha(ey?),stretchy sprites
8. Functions can return arrays. <Dynamically allocated arrays>
Dont forget:
More futureproof, faster, Line splitting, Optional Stricts & easy interface with c/c++
Great idea. But it needs to ba able to be added to the ide (for those who dont like using a browser and love f1f1)
Issues:
1. 'Code to generate a type list causes bloat'. Solution: Allow an 'autolist' declaration in each type, that creates said list behind the scenes.
2. Docs still need improvement. This may be responsible for the perceived difficulty of BlitzMax?
3. Lack of built in 3D. It's in the pipe-works. Not a lot we can do in the meantime.
4. Poor built in IDE.
1. Which not only makes it more powerful, but code can also be unbloated with things like methods etc.
2. Totally agree
3. s mark said recently, Max3D is underway in the form of a completely spanking new "B3D-like" engine lib.
4. Agreed(was b3d's much better?), but for windows theres loads of alternatives.
Non issues:
1. 'I don't like OOP'.
2. 'It isn't cute... it isn't named Blitz3D2'.
1 Dont invoke it then. Just use it as you would blitz3d.
2. Lol (someone actually said that??) you could always rename the exe & change the logo!.
BM superiorities:
1. Cross platform
2. Optimising compiler
3. OOP (ish)
4. Multiple lists per type (this one can be a positive or a negative)
5. Garbage collection is nice (when it's not causing headaches)
6. 'Out of the box' support for including media in the binary
7. '2D in 3D' out of the box... rotatey, alpha(ey?),stretchy sprites
8. Functions can return arrays. <Dynamically allocated arrays>
Dont forget:
More futureproof, faster, Line splitting, Optional Stricts & easy interface with c/c++
Lets create a community project to create high-quality documentation then.
Great idea. But it needs to ba able to be added to the ide (for those who dont like using a browser and love f1f1)