This rather bloated program hangs around on my system because I can never remember certain details. 'FBechokeys.bas - Console Mode program to echo out key values returned ' by Inkey() function. 'Ryan Kelly 2012 ' 'Compile with fbc FBechokeys.bas '_____________________________________________________...

Id like to know how fast the for next loops are and other simple commands like Print "hello" What does that have to do with language? That just jumps directly to the system console output routine? Which in 9 out of 10 languages/platforms will lead to you to the same C run time library.

reality = you + x

Both terms on the right hand side are undefined. Good luck.

Or it could be DOSBox's VGA emulation.

@1000101 This issue came to mind: http://www.freebasic.net/forum/viewtopic.php?f=3&t=18879&hilit=memory+leak It involved the use of allocate and deallocate to manage an array of strings. I've been in the habit of explicitly setting strings to null in destructors as well. I've found that expl...

But which would you rather read?

I see. But is the double cast needed?

I am not entirely sure what you are trying to accomplish here. This looks like it will evaluate to a pointer to what is probably an invalid memory address.

1000101 wrote:(when did it first get release?)

I still remember this: http://forum.qbasicnews.com/index.php?topic=7142

See http://www.freebasic.net/wiki/wikka.php ... PgOffsetof

Newbie Question! 1000101, what do you mean by "in both the gcc and gas backends." Does FB .24 not compile directly to native and support these OO features. .24 supports MORE object oriented features. Inheritance has been added. Fbc has never compiled directly to machine code. It has alway...

Since your look ahead routine is recursive, it searches depth first, which is how it gets distracted by future moves and will favor future wins that result from early moves on the left to current moves on the right. I took the same approach to scoring moves, but used a breadth first search in order ...

I see no problem with the text size. Most browsers implement simple size adjustment anyways.

Scrolling code boxes wouldn't hurt, and they are pretty simple to implement, but since I enjoyed reading the code, it never occurred to me.

1000101 wrote:Intel syntax > AT&t syntax by a land-slide.

I will never understand why the Linux community did not revolt against the GCC crowd's decision to stick with the AT&T syntax as a default.

Linux uses the UNIX "everything is a file" metaphor.