Editing True BASIC (section)

==Reception==
[[Jerry Pournelle]] in 1985 asked, "why do we need True BASIC at all? [It] doesn't seem to do anything regular BASIC doesn't do, and what it does do isn't attacked in a logical or intuitive manner." He criticized the lack of output when encountering an error, preventing interactive debugging by "[[breakpoint|inserting print statements as diagnostics]]". Pournelle concluded, "I think I'll pass up the opportunity to become a born-again True BASIC believer. I'll enjoy my [[Microsoft BASIC|Microsoft]] and [[CBASIC]] heresies."<ref name="pournelle198509">{{cite news | url=https://archive.org/stream/byte-magazine-1985-09/1985_09_BYTE_10-09_Homebrewing#page/n329/mode/2up | title=PCs, Peripherals, Programs, and People | work=BYTE | date=September 1985 | access-date=20 March 2016 | author=Pournelle, Jerry | pages=347}}</ref>

Some users have complained about their programs and the editor using up 100% of their [[CPU]] (or [[CPU core|core]]).<ref name=FirstComplaint>{{cite web|title=CPU Usage|url=http://www.truebasic.com/node/832|website=True BASIC Support Forum Dec 31, 2010|access-date=26 July 2014}}</ref><ref>{{cite web|title=CPU usage at 100%|url=http://www.truebasic.com/node/1005|website=True BASIC Support Forum Aug 22, 2012|access-date=26 July 2014}}</ref><ref>{{cite web|title=CPU usage|url=http://www.truebasic.com/node/1119|website=True BASIC Support Forum Sep 24, 2013|access-date=26 July 2014}}</ref><ref name=LastComplaint>{{cite web|title=A few more editor bugs|url=http://www.truebasic.com/node/1121|website=True BASIC Support Forum reply Feb 18, 2014|access-date=26 July 2014}}</ref> This appears to be caused by the editor and user's programs using a loop which constantly [[Polling (computer science)|polls]] the keyboard and mouse for events. The problem has been known since at least the end of 2010,<ref name=FirstComplaint /> yet as of early 2014 is still being worked on.<ref name=LastComplaint />