Macros. (and operator overloading)

I was able to rewrite the program (I remembered most of it), so it should be posted this week.

It will probably reenter the language under -lang qb at some point. The FreeBASIC language is not supposed to be a QB emulator (except -lang qb eventually), nor is it supposed to support bad practices, so it won't be supported in the official language.

If you have the CVS versions you can't use the commented forms, use

For those interested, here are the feature lists for the editor and the lexer. The bullet type indicates whether it is planned or implemented: - = implemented, + = planned FB Lexer for Scintilla - Highlighting of standard elements - identifiers, keywords, numbers, operators, etc. - Highlighting of p...

This is going to take me a while, maybe next week or next two weeks, since I just tried using it to save itself. Now the source file doesn't really contain anything. I have the exe, but that's it :( And while I'm at it, can anyone tell me how I can save a file (so the file actually saves, not a coup...

Ah. I assumed after seeing that wasn't the case, but thanks for explaining it.

The scintilla lexer will be available for Linux because it only uses Scintilla APIs, and the FBPad editor should be easy to translate.

dr0p.InStrRev(3, "QP`JYQYM]", "J")
why should this be 0? Starting on character 3 from either side, the J would be found in the string.

FBPad is a simple FB editor that will be able to compile files and do quickrun. It is meant to demonstrate the Scintilla for FB lexer that I have written, which is much better suited to FB than the VB lexer or current FB one included with scintilla. It's not meant to be a complex editor - I'm just c...

All you have to do is open the emitter file and type "output to 65xx" (obviously I'm kidding).

Not as far as I know of, but feel free to make your own.

It's not really widely supported because lots of us had problems with it.

You could probably take the print using code in the rtlib and modify it to suit your purpose.

Recursively. You actually start with the operators that have the lowest precedence, and work your way up. For example, you would call ParseExpression, which would call ParseTerm1, ParseTerm2, etc, each of which handles a certain level of operator precedence. For example, function parseExpression( ) ...