<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/lscript/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/lscript/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/lscript/bugs/</id><updated>2002-03-21T18:28:59Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>Out of Memory occurs on non-Windows box</title><link href="https://sourceforge.net/p/lscript/bugs/12/" rel="alternate"/><published>2002-03-21T18:28:59Z</published><updated>2002-03-21T18:28:59Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.netd2f2f6eeb3882bfb7a21ee4981f3c122db0df065</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Due to a lack of resources, all development for the &lt;br /&gt;
Engine thusfar has been done under Windows 95 and &lt;br /&gt;
Windows 98 machines. The code appears to compile fine &lt;br /&gt;
under the Virtual DOS Machine.&lt;/p&gt;
&lt;p&gt;However, on a recent run on a DOS machine, the engine &lt;br /&gt;
reported Out of Memory immediatly on startup. The &lt;br /&gt;
machine had more than enough available Conventional &lt;br /&gt;
and Extended Memory to be able to do it's job.&lt;/p&gt;
&lt;p&gt;Upon further investigation, there are too many SELECT &lt;br /&gt;
CASE statement in the EngLang() processor sub. &lt;br /&gt;
Windows allocates Memory differently than a Pure DOS &lt;br /&gt;
machine, one fatal design flaw we did not recognize.&lt;/p&gt;
&lt;p&gt;A review of this issue WILL need to be made &lt;br /&gt;
immediatly and a patch released ASAP.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>FUNCGetWeekDay() works incorrectly</title><link href="https://sourceforge.net/p/lscript/bugs/11/" rel="alternate"/><published>2001-12-27T21:25:25Z</published><updated>2001-12-27T21:25:25Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net905256af8eab98310fe4635b12fc5daf09cd0504</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A test of the FUNCGetWeekDay() function returns an &lt;br /&gt;
incorrect day for the date.&lt;/p&gt;
&lt;p&gt;Unknown what the cause is at current time, will &lt;br /&gt;
investigate.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>FUNCInvertString() doesn't work</title><link href="https://sourceforge.net/p/lscript/bugs/10/" rel="alternate"/><published>2001-12-27T21:24:23Z</published><updated>2001-12-27T21:24:23Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net64ab16db0248a7882816d955643adbb0578523f9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;FUNCInvertString() does not create any reversed &lt;br /&gt;
string or anything at all.&lt;/p&gt;
&lt;p&gt;The variables referenced and cross-referenced in the &lt;br /&gt;
function do not match and therefore make the function &lt;br /&gt;
do nothing.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>SysInfo() does not return correct system</title><link href="https://sourceforge.net/p/lscript/bugs/9/" rel="alternate"/><published>2001-12-19T11:29:24Z</published><updated>2001-12-19T11:29:24Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.netd9cd30b2cf281cc9cb10b6963be83005306f5878</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The SysInfo() command does not return a proper output &lt;br /&gt;
for the machine type, ex. a 286 is reported for a 486.&lt;br /&gt;
A temp fix was put into Alpha 3.0 that reported 286 &lt;br /&gt;
or 386+, however, this error needs to be investigated &lt;br /&gt;
and fixed.&lt;/p&gt;
&lt;p&gt;It is possible that more System ID Strings exist then &lt;br /&gt;
originally documented.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Bug with Script Identifier Warning</title><link href="https://sourceforge.net/p/lscript/bugs/8/" rel="alternate"/><published>2001-12-19T11:27:00Z</published><updated>2001-12-19T11:27:00Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.netdcc152dfc407743ceb4cb080ed3bf38f2eb797a4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When a script does not reference ?&amp;amp;gt;LSCRIPT in the &lt;br /&gt;
file, the error handler says in the 208 error that &lt;/p&gt;
&lt;p&gt;'Error 0x08 Occured'&lt;/p&gt;
&lt;p&gt;should be&lt;/p&gt;
&lt;p&gt;'Error 2x08 Occured'&lt;/p&gt;
&lt;p&gt;Simple typo that will be corrected in A3.1&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Leading space exists in MATH results</title><link href="https://sourceforge.net/p/lscript/bugs/7/" rel="alternate"/><published>2001-11-19T01:55:43Z</published><updated>2001-11-19T01:55:43Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.net7846d6b63f3821130bab72f90dfb8db8ed39afe9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A leading space exists when returning Math results.&lt;br /&gt;
A line that should print:&lt;/p&gt;
&lt;p&gt;2&lt;/p&gt;
&lt;p&gt;Prints:&lt;/p&gt;
&lt;p&gt;2&lt;/p&gt;
&lt;p&gt;Tried using FIX in latest internal build, however, &lt;br /&gt;
problem does not seem to clear up. Assigned to &lt;br /&gt;
project lead. Will investigate.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>MoveFile() / MoveFileB() needs checking</title><link href="https://sourceforge.net/p/lscript/bugs/6/" rel="alternate"/><published>2001-11-05T14:52:08Z</published><updated>2001-11-05T14:52:08Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.netd745b224b46836f7562949cfac4a70ddb0726825</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;InFile$, OutFile$ may not apply to VarA,VarB base &lt;br /&gt;
rules and need to be reviewed for operatibility. &lt;br /&gt;
Correct as neccessary - not checked but believed to be &lt;br /&gt;
incorrectly programmed...&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Variables need updating</title><link href="https://sourceforge.net/p/lscript/bugs/5/" rel="alternate"/><published>2001-11-05T14:49:25Z</published><updated>2001-11-05T14:49:25Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.net1b2ca13663aaafc5a33b08159bd3b3a60186a6c7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A checkover of the variables list in all modules needs &lt;br /&gt;
to be updated with the recent additions to the main &lt;br /&gt;
program module. Not confirmed, however, believed to &lt;br /&gt;
need updating. Will check.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>PrnVar() needs updating</title><link href="https://sourceforge.net/p/lscript/bugs/4/" rel="alternate"/><published>2001-11-04T13:03:48Z</published><updated>2001-11-04T13:03:48Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.net7a86971743e2e1483948a95631dd218e58581390</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;PrnVar() may not print out all of the available &lt;br /&gt;
variables at this time. Lcomp is checking to make &lt;br /&gt;
sure that all variables are present for 2.0.2-dev&lt;/p&gt;
&lt;p&gt;Developers - Report any problems, please.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>FUNCScrMode() Object bug</title><link href="https://sourceforge.net/p/lscript/bugs/3/" rel="alternate"/><published>2001-10-28T21:42:46Z</published><updated>2001-10-28T21:42:46Z</updated><author><name>Chris Formeister</name><uri>https://sourceforge.net/u/lcompmicro/</uri></author><id>https://sourceforge.neta19dbd7b2c2b2a2ea1c6c71dce304b2cc2a8b92e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When changing over certain screen objects from one &lt;br /&gt;
screen mode to another, a severe error may occur that &lt;br /&gt;
returns the engine to the command prompt without &lt;br /&gt;
proper processing.&lt;/p&gt;
&lt;p&gt;EX.&lt;/p&gt;
&lt;p&gt;Changing screen mode with a certain object or item &lt;br /&gt;
for that screen mode to another that it isn't &lt;br /&gt;
compatible with.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>