MBasic 1.5 
Author Message
 MBasic 1.5

Major update available here:

http://www.*-*-*.com/

FC.



Thu, 14 Jul 2005 07:22:31 GMT  
 MBasic 1.5

Quote:

>Major update available here:

>http://membres.lycos.fr/hitchhikr/MBasic.html

I especially like this feature:

 "Pre-compilation engine to reach speed of light"

That's almost as fast as powerbasic/CC, which can
complete an infinite loop in 2.73 seconds.

--

</head><body><a href="http://www.guymacon.com/resume.html">Electrical
engineer</a> for hire: Los Angeles/Orange County CA USA, 714-670-1687
<br />See resume at: http://www.guymacon.com/resume.html</body><html>



Thu, 14 Jul 2005 12:22:48 GMT  
 MBasic 1.5

Quote:

> "Pre-compilation engine to reach speed of light"


Quote:
>That's almost as fast as PowerBASIC/CC, which can
>complete an infinite loop in 2.73 seconds.

Any good optimizing compiler should be able to detect infinite loops
and remove them, making the execution time "negligible" - hahaha.


Thu, 14 Jul 2005 19:31:12 GMT  
 MBasic 1.5


Quote:

>> "Pre-compilation engine to reach speed of light"


>>That's almost as fast as PowerBASIC/CC, which can
>>complete an infinite loop in 2.73 seconds.

>Any good optimizing compiler should be able to detect infinite loops
>and remove them, making the execution time "negligible" - hahaha.

That would be a compiler bug.  A good optimizing compiler should
detect and delete a never-executed loop, but an infinite loop might be
deliberate.  Consider the outermost loop of an OS command interpreter.


Fri, 15 Jul 2005 13:57:07 GMT  
 MBasic 1.5

Quote:




>>>>Major update available here:

>>>>http://membres.lycos.fr/hitchhikr/MBasic.html

>>>I especially like this feature:

>>> "Pre-compilation engine to reach speed of light"

>>>That's almost as fast as PowerBASIC/CC, which can
>>>complete an infinite loop in 2.73 seconds.

>>Any good optimizing compiler should be able to detect
>>infinite loops and remove them, making the execution
>>time "negligible" - hahaha.

>That would be a compiler bug.  A good optimizing compiler
>should detect and delete a never-executed loop, but an
>infinite loop might be deliberate.  Consider the outermost
>loop of an OS command interpreter.

Also, detecting all infinite loops requires solving
Turing's Halting Problem, which is impossible. See
http://www.cs.washington.edu/homes/csk/halt.html

--
Guy Macon Guy Macon Guy Macon Guy Macon Guy Macon Guy Macon Guy Macon
<html><head></head><body><a href="http://www.guymacon.com/resume.html">
Electrical engineer</a> for hire: Los Angeles/Orange County CA USA
<br />See resume at: http://www.guymacon.com/resume.html</body><html>
Guy Macon Guy Macon Guy Macon Guy Macon Guy Macon Guy Macon Guy Macon



Fri, 15 Jul 2005 22:33:41 GMT  
 MBasic 1.5
-> That would be a compiler bug.  A good optimizing compiler should
-> detect and delete a never-executed loop, but an infinite loop might be
-> deliberate.  Consider the outermost loop of an OS command
-> interpreter.

A loop that would always produce the same result when it is executed
should be deleted. One that can produce differing results, because of
differing inputs, should be retained.

                             dow



Fri, 15 Jul 2005 23:02:41 GMT  
 
 [ 8 post ] 

 Relevant Pages 

1. VB5EE setup wizard and mdac 1.5 (ado 1.5) problem

2. Display 1.50 and not 1.5

3. Help; Centura 1.5, CDO

4. TURBO*LIBRARY 1.5

5. LDAP connection with ADO 1.5

6. OsloData 1.5 :New DB SHAREWARE

7. QuickFORM 1.5 now shipping

8. Announcing WinBrowse 1.5 - Multi database utility and browser

9. NewWorld3D 1.5 OCX update - screen shots

10. ADO 1.5 CMD error when executing Stored Procedures??

11. ActiveExec 1.5 Released!

12. ActiveExec 1.5 - Need Beta Testers!

 

 
Powered by phpBB® Forum Software