--


Thank you for helping to test QB64

by (no login)

 
Firstly, I'd like to thank Qbguy who contributed so many example programs for QB64 and has tested many BASIC programs (Eliza, a Morse Code Converter, fake Vista Installer, Battle Ship) for compatibility. I'm pleased they were able to work in such an early demo of QB64. All your posts were most welcome.

I'd also like to that Mennonite, Pete, MystikShadows and Roy for the effort they have put into testing Demo #5.

RE: Recently reported incompatibilities:

i) ELSEIF/ELSE bug
I didn't know QB allowed statements on the same line after an ELSE or ELSEIF statement. Consider it fixed for Demo #6. Though I too find it strange that in the following example an END IF isn't implied by having a statement after the block ELSE (as in the following case Pete presented).
IF A = 10 THEN
GOSUB TEST
ELSE GOSUB FINISH
END IF

ii) It was reported that following code only PRINTs 44 characters per MINUTE:
CLS
DO
b$ = INKEY$
IF b$ = CHR$(27) THEN END
IF b$ <> "" THEN PRINT b$;
LOOP
I tested this, holding down a key (so aonly at the speed of the normal key repeat rate) it printed approx. 80 charcters (one line) in 5 seconds. The reason it was slow is because thread timing hasn't been implemented properly yet (it very soon will be), your programs main thread is hogging CPU time and not allowing the update screen (this part also needs to be revised for speed, it will later become at least 50x faster for text modes) and read windows messages thread. Expect this to work fine in Demo #6.

iii) "in qb (and fb,) print val("&h"+str$(20)) prints 32
print &h20 works.
val("&o"+q$) should convert q$ to octal."
WOW, I thought I knew QB inside out! I knew all about &H... and the HEX$ and OCT$ functions but didn't realise &O... worked as well. I'm sure this can also be fixed for Demo #6.

iv) "INPUT bug. cursor does not cursor back under characters when arrow left key is used."
I haven't worked out all the kinks in the way the INPUT statement will work yet. When certain characters are PRINT'ed to the screen QB64 also needs to do things like perform a CLS.

Posted on Jan 29, 2008, 1:28 AM

Respond to this message   

Return to Index

Response TitleAuthor and Date
*I'd also like to *thank* Mennonite, Pete, MystikShadows and Roy... on Jan 29
That's good news on INKEY$...Pete on Jan 29
SuggestionOLPC on Jan 29
 isn't there a way to make a compiler make exe's that don't hog the cpu every loop anyway?mennonite on Jan 29
  my own experience has been thismennonite on Jan 29
  Nope, it is a programming thing with threads...rpgfan3233 on Jan 29
   so i'll bow to your knowledge on this rpg, it's not possible?mennonite on Jan 29
    Windows has nothing to do with it. :-POLPC on Jan 29
     oh forgive me!mennonite on Jan 29
      also how well does wait &h3da, 8 work for this?mennonite on Jan 29
       Not sure...OLPC on Jan 29
        i'll be sure to try it with qb64 latermennonite on Jan 29
      PrioritiesOLPC on Jan 29
       coolmennonite on Jan 29
        In Windows 2000, it's...OLPC on Jan 29
         *thanks, same in xpmennonite on Jan 29
  Of course there is...OLPC on Jan 29
   i've used that solutionmennonite on Jan 29
    and if you say "well that kind of solution would make everything suck"mennonite on Jan 29
    I can't think of a way to do this automaticallyOLPC on Jan 29
     you're probably rightmennonite on Jan 29
Bug: INPUT won't handle numeric variables correctly unless...Dav on Jan 29
 I forgot to add ...Dav on Jan 29
 LOL @ more interesting than election returns... About the speed.Pete on Jan 29
  * I don't suppose you want an FB plug here. :-)OLPC on Jan 29
  Stats for a 100k source compile....Dav on Jan 30
   Isn't it amazing how fast the QuickBasic Compiler is?Pete on Jan 30
    * That was my first thought as well.Dav on Jan 30
    Well that's easy to figure out on Feb 2
   FreeBASIC stats (FWIW)OLPC on Jan 31
Speed, delays, OS's, multi-threading on Jan 30
 Interesting post. I tried to get to the end of it but it burnt up my CPU...Pete on Jan 30

 Copyright © 1999-2008 Network54. All rights reserved.   Terms of Use   Privacy Statement