Macros are good for adding hidden high level structures. I would support a much more featured macro pre-compiling syntax...
boriel wrote:blah blah blah ...lists.
Using Macros mean the *preprocessor* (not the compiler) is in charge of the part the language can't manage: you're trying to do something you can't program in FreeBASIC.
Macros are a bad idea because it's changing your source code on the fly: Read here
(yes, Googlers also think that way).
agamemnus wrote:Built-in not a bad idea as an add-on, but all new additions should be balanced and there should be much consideration as to syntax. You said yourself the syntax is "polluted".. what do you think auto-lists will do??
I didn't said that: I meant current FreeBASIC syntax is low level, and programing complex data structures makes your code dirty (e.g. you need to write much text to implement such things).
Auto-list (or the list example) is a way to make programs clearer.
agamemnus wrote:You would need to implement them very, very carefully to avoid interfering with the current syntax. Considering that we have very few developers (currently, dkl and cha0s, and sometimes countingpine), I think the effort should still be focused on refining current features and bug-fixing...
Of course! (I do the same when fixing my tiny 8bit FreeBASIC clone). First things first (IMHO, ByVal strings should be in the 1st place).
Poor lil' dev marionettes! They will bow to the will of our discussion, when all is said and done. :(
Don't be so negative. I was talking in the long term
. How will FreeBASIC be (as a language) next year? and in 2015? and in 2020? Imagine that for a while. Yes, it could be dead. It could also evolve to a higher level syntax, or it could just stagnate and stay as is so people will develop more libraries (or whatever)....
I don't use FreeBASIC at this moment (I use C++ for speed critical things, and python for the rest). But I *love* the language and the tools around it, and if it finally dies, it would be very sad :(