Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
opinions needed - designing an IDE
#21
how about

Code:
PRINT "Mouse-turn-on-thing utility"
PRINT
ASM
     ;Some Random ASM code here
     mov ax,1
     int 33
END ASM
END
Dunno if it would -work-, just sounded interesting. :rotfl:
size=9]"To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public." -- Theodore Roosevelt[/size]
Reply
#22
If I decided to support inline asm, it would probably be limited to 386 instructions at first, unless I rely on masm for syntax checking of asm, in which case I'd have to work out a way of catching them and reporting them in the IDE.

And because of the issue of variables with names like AX it might require you to prepend a certain one or two characters to all variable names... maybe just an underscore (_).
Reply
#23
Quote:I *need* syntax highlighting ;)
Hmm... syntax highlighting looks a lot better on a white background than on blue. I might switch it to Windows just for that. I can't decide what could look ok - pick your favorite color(s):
[Image: print.png]
Reply
#24
Let me ask you a question: what's wrong with QB's color options feature....?
Peace cannot be obtained without war. Why? If there is already peace, it is unnecessary for war. If there is no peace, there is already war."

Visit www.neobasic.net to see rubbish in all its finest.
Reply
#25
Quote:
Quote:'$define
(see #define in c/c++)

There are good reasons why C has a preprocessor and good reasons why other languages such as Java and QBasic do not have one. A good language includes a feature because it is a useful addition, not a cool novelty, QBasic in particular does not need a preprocessor.

Well I thought it could be useful since I debugged a program in C++
with it. (Yeah I know there's some #debug stuff and such but I've
never learned it. so I made a debugging feature like this:
Code:
#define q debug_function;

void debug_function();
int debug_var=0

int main()
{
//code
q
//code I suspect causes a n error
q
code
}

void debug_function()
{
ddebug_var++
//open c:\debuglog, print debug_var, close debuglog
}

Well something like that...
/post]
Reply
#26
Quote:Let me ask you a question: what's wrong with QB's color options feature....?
It doesn't support syntax highlighting - all the text must be the same color in QB.
Reply
#27
I think he means why not let the programmer pick the color of the text/background, similar to the QB IDE. (It would work the same way with syntax highlighting, you'd have more options to set up.)
Reply
#28
Plasma357: OIC, ok.
Reply
#29
Eh??? What I mean by syntax highlighting is:

open quanta
start writing some php

*That* is syntax highlighting. Different colours for variables, commands...

And yes, it would look better on white.
Reply
#30
Pink! Pink is the way to go.......

GREY ON BLUE
GREY ON BLUE
RARARA...
Peace cannot be obtained without war. Why? If there is already peace, it is unnecessary for war. If there is no peace, there is already war."

Visit www.neobasic.net to see rubbish in all its finest.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)