https://scarlet.deltasoft.com/api.php?action=feedcontributions&feedformat=atom&user=GlenbScarletDME - User contributions [en]2026-08-23T02:46:13ZUser contributionsMediaWiki 1.46.0https://scarlet.deltasoft.com/index.php?title=Installers&diff=506Installers2010-02-14T23:02:55Z<p>Glenb: /* Deb */</p>
<hr />
<div>Development of installation assiters or binary distribution packages.<br />
<br />
===RPM===<br />
It exists, it need documenting and making into a auto build process on the gpl.openqm server. Contact [[User:Diccon|Diccon]] for info.<br />
<br />
===Deb===<br />
For Ubuntu, Debian, and other debian based distros.<br />
<br />
Debian package, a classic one exists. It can be done again. [[User:GlenB|GlenB]] is the contact for this.<br />
<br />
A bundle of build and publish scripts, repository formats/files, and various source files can be found [http://www.scarletdme.org/downloads/qmdeb-pkg-files.tgz here]. This bundle includes the source releases of the OpenQM project and all of the files must be rebranded to reflect the ScarletDME project name.<br />
<br />
===Distro neutral script===<br />
This is an idea at the moment, mainley aimed at developers. If you have an install of QM already you might want to quickly setup multiple QM directorys/version on one server, to allow you to play around. <br />
<br />
To achieve this a distro neutral script could be written to se the current dir of QM to be the current running one.<br />
*Move out QM.config in /etc, place an apropriate one for current dir<br />
*check for groups, qm, and qmdev, create if missing. <br />
*move or link to /usr/bin/qm (and other binarys)<br />
<br />
This should be non destructive and able allow reinstantiation of previous installs.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Installers&diff=505Installers2010-02-14T22:58:43Z<p>Glenb: /* Deb */</p>
<hr />
<div>Development of installation assiters or binary distribution packages.<br />
<br />
===RPM===<br />
It exists, it need documenting and making into a auto build process on the gpl.openqm server. Contact [[User:Diccon|Diccon]] for info.<br />
<br />
===Deb===<br />
For Ubuntu, Debian, and other debian based distros.<br />
<br />
Debian package, a classic one exists. It can be done again. [http://www.scarletdme.org/wiki/User:GlenB GlenB] is the contact for this.<br />
<br />
===Distro neutral script===<br />
This is an idea at the moment, mainley aimed at developers. If you have an install of QM already you might want to quickly setup multiple QM directorys/version on one server, to allow you to play around. <br />
<br />
To achieve this a distro neutral script could be written to se the current dir of QM to be the current running one.<br />
*Move out QM.config in /etc, place an apropriate one for current dir<br />
*check for groups, qm, and qmdev, create if missing. <br />
*move or link to /usr/bin/qm (and other binarys)<br />
<br />
This should be non destructive and able allow reinstantiation of previous installs.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=User:GlenB&diff=504User:GlenB2010-02-14T22:57:45Z<p>Glenb: New page: Glen Batchelor: [mailto:batchelg@bellsouth.net E-Mail] [http://twitter.com/pickcoder Twitter]</p>
<hr />
<div>Glen Batchelor: [mailto:batchelg@bellsouth.net E-Mail] [http://twitter.com/pickcoder Twitter]</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=403Custom Compiler Modes2009-04-26T04:21:06Z<p>Glenb: /* OpenQM GPL Custom Compiler Modes */</p>
<hr />
<div><br />
== OpenQM GPL Compatibility Compiler Modes ==<br />
<br />
===HEADING.NO.EJECT===<br />
This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
<br />
===NO.ECHO.DATA=== <br />
This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
<br />
----<br />
<br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
===NO.CASE.INVERT=== <br />
This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=402Custom Compiler Modes2009-04-26T04:20:46Z<p>Glenb: /* OpenQM GPL Compatibility Compiler Modes */</p>
<hr />
<div><br />
== OpenQM GPL Compatibility Compiler Modes ==<br />
<br />
===HEADING.NO.EJECT===<br />
This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
<br />
===NO.ECHO.DATA=== <br />
This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
<br />
----<br />
<br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
'''NO.CASE.INVERT''' - This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=401Custom Compiler Modes2009-04-26T04:20:29Z<p>Glenb: /* OpenQM GPL Compatibility Compiler Modes */</p>
<hr />
<div><br />
== OpenQM GPL Compatibility Compiler Modes ==<br />
<br />
===HEADING.NO.EJECT=== - This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
<br />
===NO.ECHO.DATA=== - This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
<br />
----<br />
<br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
'''NO.CASE.INVERT''' - This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=400Custom QMBASIC Options2009-04-26T04:05:20Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
===INPUT===<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
===INPUT@===<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
===SOCKET.INFO===<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=399Custom QMBASIC Options2009-04-26T04:05:06Z<p>Glenb: /* INPUT */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table of Contents'''<br />
[[#INPUT]]<br />
<br />
<br />
===INPUT===<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
===INPUT@===<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
===SOCKET.INFO===<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=398Custom QMBASIC Options2009-04-26T04:04:41Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table of Contents'''<br />
[[#INPUT]]<br />
<br />
<br />
===INPUT===<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=397Custom QMBASIC Options2009-04-26T04:03:14Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table of Contents'''<br />
[[#INPUT]]<br />
<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=396Custom QMBASIC Options2009-04-26T04:00:54Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=395Custom QMBASIC Options2009-04-26T04:00:25Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table Of Contents'''<br />
<nowiki> <br />
<a href="#input">INPUT</a><br />
<a href="#inputat">INPUT@</a><br />
<a href="#socket.info">SOCKET.INFO</a><br />
</nowiki><br />
<br />
<a name="#inputat">'''INPUT@'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#inputat">'''INPUT@'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#socket.info">'''SOCKET.INFO'''</a><br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=394Custom QMBASIC Options2009-04-26T03:59:44Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table Of Contents'''<br />
<nowiki> <br />
<a href="#input">INPUT</a><br />
<a href="#inputat">INPUT@</a><br />
<a href="#socket.info">SOCKET.INFO</a><br />
</nowiki><br />
<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#inputat">'''INPUT@'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#socket.info">'''SOCKET.INFO'''</a><br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=393Custom QMBASIC Options2009-04-26T03:58:12Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table Of Contents'''<br />
[#input INPUT]<br />
[#inputat INPUT@]<br />
[#socket.info SOCKET.INFO]<br />
<br />
<br />
<br />
<a name="#input">'''INPUT'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#inputat">'''INPUT@'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#socket.info">'''SOCKET.INFO'''</a><br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=392Custom QMBASIC Options2009-04-26T03:52:28Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''Table Of Contents'''<br />
<a href="#input">INPUT</a><br />
<a href="#inputat">INPUT@</a><br />
<a href="#socket.info">SOCKET.INFO</a><br />
<br />
<br />
<br />
<a name="#input">'''INPUT'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#inputat">'''INPUT@'''</a><br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
<a name="#socket.info">'''SOCKET.INFO'''</a><br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=391Custom QMBASIC Options2009-04-26T03:51:00Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=390Custom QMBASIC Options2009-04-26T03:50:29Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />Example Code:<br /><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />Example Code:<br /><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=389Custom QMBASIC Options2009-04-26T03:50:02Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br /><b>Example Code:</b><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=388Custom QMBASIC Options2009-04-26T03:49:45Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<hr /><b>Example Code:</b><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=387Custom QMBASIC Options2009-04-26T03:49:32Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
---<br />
<b>Example Code:</b><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=386Custom QMBASIC Options2009-04-26T03:48:52Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
<b>NOCASEINVERT</b> - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
<b>SKT$INFO.FAMILY</b> - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br /><b>Example Code:</b><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=385Custom QMBASIC Options2009-04-26T03:47:55Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br /><b>Example Code:</b><br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
''SKT$INFO.FAMILY'' - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br /><b>Example Code:</b><br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=384Custom QMBASIC Options2009-04-26T03:47:24Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
<b>Example Code:</b><br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
Example Code:<br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
''SKT$INFO.FAMILY'' - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />
Example Code:<br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=383Custom QMBASIC Options2009-04-26T03:46:46Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''Example Code:'''<br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''Example Code:'''<br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
''SKT$INFO.FAMILY'' - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
<br />
'''Example Code:'''<br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=382Custom QMBASIC Options2009-04-26T03:46:12Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
Example Code:<br />
INPUT MYVAR NOCASEINVERT<br />
<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
Example Code:<br />
INPUT@(0,0) MYVAR NOCASEINVERT<br />
<br />
<br />
'''SOCKET.INFO'''<br />
''SKT$INFO.FAMILY'' - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT$INFO.FAMILY.IPV6 - This value means the open socket is IPv6<br />
Example Code:<br />
SKTFAMILYTYPE = SOCKET.INFO(SKTHANDLE,SKT$INFO.FAMILY)<br />
BEGIN CASE<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV4; CRT "This is an IPv4 socket!"<br />
CASE SKTFAMILYTYPE = SKT$INFO.FAMILY.IPV6; CRT "This is an IPv6 socket!"<br />
END CASE</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=381Custom QMBASIC Options2009-04-26T03:43:26Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''SOCKET.INFO'''<br />
''SKT$INFO.FAMILY'' - This key was added to support the identification of IPv4 and IPv6 family types on an open socket handle.<br />
SKT@$INFO.FAMILY.IPV4 - This value means the open socket is IPv4<br />
SKT@$INFO.FAMILY.IPV6 - This value means the open socket is IPv6</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Downloads&diff=380Downloads2009-04-25T03:24:30Z<p>Glenb: /* Packages */</p>
<hr />
<div>Files, sources, packages and apps for OpenQM<br />
<br />
==Packages==<br />
*RPM package - [http://gpl.openqm.com/downloads/openqm-2.6-6.i386.rpm openqm-2.6-6.i386.rpm]<br />
*Debian Package - [http://gpl.openqm.com/downloads/openqm_2.4.17_all.deb openqm_2.4.17_all.deb] (Note 2-4-4 built only atm)<br />
*Debian Package - [http://gpl.openqm.com/downloads/openqm-gpl_2.6.6_all.deb openqm-gpl_2.6.6_all.deb] (Note: this needs testing for upgrades)<br />
<br />
==Source==<br />
Original Ladybridge Source Tarballs<br />
<br />
*[http://gpl.openqm.com/downloads/qmsrc_2-6-6.tgz qmsrc_2-6-6.tgz]<br />
*[http://gpl.openqm.com/downloads/qmsrc_2-4-4.tgz qmsrc_2-4-4.tgz]<br />
<br />
<br />
For latest build, issue this command in Linux for OpenQMVDB build ('''''Recommended''''')<br />
svn checkout https://gpl.openqm.com/svn/qmvdb<br />
''(Requires subversion client)''<br />
<br />
<br />
==Applications==<br />
*Coyote PICK webserver - [http://gpl.openqm.com/downloads/qmweb-gpl-2006-03-11.tar.gz qmweb-gpl-2006-03-11.tar.gz] - N.B. The source code for the daemon is missing.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Downloads&diff=379Downloads2009-04-25T03:24:15Z<p>Glenb: /* Packages */</p>
<hr />
<div>Files, sources, packages and apps for OpenQM<br />
<br />
==Packages==<br />
*RPM package - [http://gpl.openqm.com/downloads/openqm-2.6-6.i386.rpm openqm-2.6-6.i386.rpm]<br />
*Debian Package - [http://gpl.openqm.com/downloads/openqm_2.4.17_all.deb openqm_2.4.17_all.deb] (Note 2-4-4 built only atm)<br />
*Debian Package - [http://gpl.openqm.com/downloads/openqm-gpl_2.6.6_all.deb] openqm-gpl_2.6.6_all.deb (Note: this needs testing for upgrades)<br />
<br />
==Source==<br />
Original Ladybridge Source Tarballs<br />
<br />
*[http://gpl.openqm.com/downloads/qmsrc_2-6-6.tgz qmsrc_2-6-6.tgz]<br />
*[http://gpl.openqm.com/downloads/qmsrc_2-4-4.tgz qmsrc_2-4-4.tgz]<br />
<br />
<br />
For latest build, issue this command in Linux for OpenQMVDB build ('''''Recommended''''')<br />
svn checkout https://gpl.openqm.com/svn/qmvdb<br />
''(Requires subversion client)''<br />
<br />
<br />
==Applications==<br />
*Coyote PICK webserver - [http://gpl.openqm.com/downloads/qmweb-gpl-2006-03-11.tar.gz qmweb-gpl-2006-03-11.tar.gz] - N.B. The source code for the daemon is missing.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=User:Glenb&diff=376User:Glenb2009-04-23T02:42:03Z<p>Glenb: New page: Just another geek that loves Pick. I'm into small scale R/C and have a tricked HPI RS4 M/T and a HeliMax CPv3 heli(which I still can't fly well) I used to run PickSource, but it failed du...</p>
<hr />
<div>Just another geek that loves Pick.<br />
<br />
I'm into small scale R/C and have a tricked HPI RS4 M/T and a HeliMax CPv3 heli(which I still can't fly well)<br />
I used to run PickSource, but it failed due to a lack of decent content contributions other than my own. This is my last attempt at a GPL project so I hope it succeeds.<br />
Employed by All-Spec Industries since Dec 1996 as IT Director, CIO, network admin, etc et all. http://www.all-spec.com<br />
Married to a great wife/mom, April, with fraternal twin daughters Sarah and Naomi.<br />
<br />
My background is in EE(digital circuit design), but I never had a chance to apply it. I obtained an ASEE, transferred to UNC Charlotte and got burned out my senior year. I went to work at All-Spec during that time and have been growing with the company since then. I plan on obtaining my CS degree when time allows.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Wish_list&diff=375Wish list2009-04-23T02:23:18Z<p>Glenb: </p>
<hr />
<div>Things we need or want.<br />
<br />
If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.<br />
<br />
To keep in touch with this slowly evolving agenda register, making sure your preferences[http://gpl.openqm.com/wiki/Special:Preferences] include "E-mail me when a page on my watchlist is changed", and that you are logged in, and click the "watch" tab at the top of this page.<br />
<br />
==Development==<br />
{| class="wikitable"<br />
|-<br />
! Wished<br />
! Diccon<br />
! Karaken12<br />
! Ashley<br />
! DanW<br />
! SteveB<br />
! Geneb<br />
! 7<br />
! 8<br />
! 9<br />
! 0<br />
! 1<br />
! 2<br />
! 3<br />
! 4<br />
! 5<br />
! 6<br />
! 7<br />
! 8<br />
! 9<br />
! 0<br />
|-<br />
|Accumulate Existing bugfixes into subversion - '''IMPORTANT'''; Can anyone with existing bug fixes please email [[Admin Team]] or commit them into our subversion trunk [[HOWTO]]. (1 Done Thanks Ashley)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Lastest version DEB package<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|QM API list compression<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|XML Database layer<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|XQuery Engine<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Interface to Maverick running inside a JVM in a web-browser so as to implement client-side form processing in multivalue BASIC.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Specific flavoured compatibility modes (eg D3 mode, Sequoia mode)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Code porting program, similar to jBase's PORT.BAS (ideal for Perl regexp?)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|QM BASIC Subversion client wrapper - Simple way to get Pickies onboard. - '''TAKEN''' - [[User:Karaken12|Karaken12]] I've already done this, although it does need some cleaning up.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|QM Virtual File System (VFS) for some SQL database(s)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Pref to set SCROLL option as default ON for all access statements<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|"FOR EACH" BASIC syntax (Like perl and other languages)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Utility to use dictionary names for handling a record instead of direct AM addressing (possibly using OO QM) - '''In-Dev''' - [[User:Glenb|Glenb]] - workdevbranch1 GPL.BP has a DICT.TOOLS.CLS QMOO class for testing and development. Writing via dicts is not yet functional; discussion needed on I-types.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Enhancment to the Cygwin Windows port to address poor IPC performance.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|}<br />
<br />
Notes:<br />
#Digits mean nothing and are just to make it easier to edit the weird wiki table format.<br />
#If you have a column, please change your digit to indicate any preferences eg + ++ ++ - -- ---. You can use empty columns and add your name in the column heading or add more columns.<br />
<br />
==Sysadmin==<br />
*Sort /var/www or Apache so we dont have to multi sym link to get dirs visible. - '''TAKEN''' - [[User:DanW|DanW]] I'll sort this, I think a simple landing page with links to the various bits of the system will simplify our directory structure somewhat.<br />
<strike>*ftp access? (not sure if we need this) '''TAKEN''' - [[User:DanW|DanW]] - I can set up SFTP access, somewhat more secure than FTP</strike> See [[SFTP]]<br />
*SVN compatibility/capability with hashed files<br />
<strike>*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.</strike> - [http://gpl.openqm.com/bugzilla Bugzilla up]<br />
<br />
==Bugfixes==<br />
[[List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)]]<br />
<br />
==General Bright Ideas==<br />
* point SORTWORK to a RAMFS mount, would provide very fast sort handling. (Ashley notes: Altering the SORTMEM parameter does the same)<br />
* A bit blue-sky, but something I've wanted to work on for ages: full Unicode support.<br />
* Construct a "High performance" benchmark and tuning section<br />
*Define a "core" of standardised multivalue capabilities that is implemented in all systems, so porting between systems requires zero modifications.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Wish_list&diff=374Wish list2009-04-23T02:22:44Z<p>Glenb: </p>
<hr />
<div>Things we need or want.<br />
<br />
If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.<br />
<br />
To keep in touch with this slowly evolving agenda register, making sure your preferences[http://gpl.openqm.com/wiki/Special:Preferences] include "E-mail me when a page on my watchlist is changed", and that you are logged in, and click the "watch" tab at the top of this page.<br />
<br />
==Development==<br />
{| class="wikitable"<br />
|-<br />
! Wished<br />
! Diccon<br />
! Karaken12<br />
! Ashley<br />
! DanW<br />
! SteveB<br />
! Geneb<br />
! 7<br />
! 8<br />
! 9<br />
! 0<br />
! 1<br />
! 2<br />
! 3<br />
! 4<br />
! 5<br />
! 6<br />
! 7<br />
! 8<br />
! 9<br />
! 0<br />
|-<br />
|Accumulate Existing bugfixes into subversion - '''IMPORTANT'''; Can anyone with existing bug fixes please email [[Admin Team]] or commit them into our subversion trunk [[HOWTO]]. (1 Done Thanks Ashley)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Lastest version DEB package<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|QM API list compression<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|XML Database layer<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|XQuery Engine<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Interface to Maverick running inside a JVM in a web-browser so as to implement client-side form processing in multivalue BASIC.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Specific flavoured compatibility modes (eg D3 mode, Sequoia mode)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Code porting program, similar to jBase's PORT.BAS (ideal for Perl regexp?)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|QM BASIC Subversion client wrapper - Simple way to get Pickies onboard. - '''TAKEN''' - [[User:Karaken12|Karaken12]] I've already done this, although it does need some cleaning up.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|QM Virtual File System (VFS) for some SQL database(s)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Pref to set SCROLL option as default ON for all access statements<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|"FOR EACH" BASIC syntax (Like perl and other languages)<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Utility to use dictionary names for handling a record instead of direct AM addressing (possibly using OO QM) - '''In-Dev''' - [[User:GlenB|GlenB]] - workdevbranch1 GPL.BP has a DICT.TOOLS.CLS QMOO class for testing and development. Writing via dicts is not yet functional; discussion needed on I-types.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|Enhancment to the Cygwin Windows port to address poor IPC performance.<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br />
|-<br />
|}<br />
<br />
Notes:<br />
#Digits mean nothing and are just to make it easier to edit the weird wiki table format.<br />
#If you have a column, please change your digit to indicate any preferences eg + ++ ++ - -- ---. You can use empty columns and add your name in the column heading or add more columns.<br />
<br />
==Sysadmin==<br />
*Sort /var/www or Apache so we dont have to multi sym link to get dirs visible. - '''TAKEN''' - [[User:DanW|DanW]] I'll sort this, I think a simple landing page with links to the various bits of the system will simplify our directory structure somewhat.<br />
<strike>*ftp access? (not sure if we need this) '''TAKEN''' - [[User:DanW|DanW]] - I can set up SFTP access, somewhat more secure than FTP</strike> See [[SFTP]]<br />
*SVN compatibility/capability with hashed files<br />
<strike>*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.</strike> - [http://gpl.openqm.com/bugzilla Bugzilla up]<br />
<br />
==Bugfixes==<br />
[[List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)]]<br />
<br />
==General Bright Ideas==<br />
* point SORTWORK to a RAMFS mount, would provide very fast sort handling. (Ashley notes: Altering the SORTMEM parameter does the same)<br />
* A bit blue-sky, but something I've wanted to work on for ages: full Unicode support.<br />
* Construct a "High performance" benchmark and tuning section<br />
*Define a "core" of standardised multivalue capabilities that is implemented in all systems, so porting between systems requires zero modifications.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=List_of_fixed_bugs_in_the_commercial_version_of_OpenQM_(Current_as_of_2.8-10)&diff=373List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)2009-04-16T03:42:54Z<p>Glenb: </p>
<hr />
<div>The list of fixed issues below are in reverse version order. If one is fixed, please use the <nowiki><strike></strike></nowiki> html command to block out the fixed bug.<br />
<br />
*2.8-10<br />
The QMBasic compiler allowed use of EQ as an alternative to the = symbol as an<br />
assignment operator.<br />
<br />
Query commands that used closed range tests (e.g. A > 5 and < 8) with fields<br />
for which an alternate key index was present could return incorrect data.<br />
<br />
*2.8-9<br />
The N() funcion in an A-correlative did not allow for field names that did not<br />
comply with QM's naming rules.<br />
<br />
Where a file had multiple alternate key indices, if an index was built from a<br />
calculated value that used a T-conversion or a TRANS() function to reference a<br />
record that did not exist, all later index updates for the same write would<br />
damage the index.<br />
<br />
Use of PSTAT could cause the process being queried to crash if it had a very<br />
deep execution stack or was executing a very long command. <br />
<br />
A phantom would fail to start correctly if the parent process terminated before<br />
it had commenced its initialisation.<br />
<br />
The Proc A command did not treat semicolons in the source data as a special<br />
character separating multiple items.<br />
<br />
A Proc with a command of H with no qualifying text caused the Proc processor<br />
to loop.<br />
<br />
The LPTR keyword was not recognised by the FILE.STAT command.<br />
<br />
The WHEN clause of the query processor was not handling some complex conditions<br />
correctly.<br />
<br />
A Pick style qualified display clause on a multivalued field was equivalent to<br />
use of WITH when it should have been equivalent to use of WHEN.<br />
<br />
Quitting out of a PSTAT command could result in not being able to start pahntom<br />
processes.<br />
<br />
<strike>The @FILENAME synonym for @FILE.NAME was not recognised by the QMBasic<br />
compiler.</strike><br />
<br />
The QMBasic OPENSEQ statement did not return the blocking user number via the<br />
STATUS() function if the record was locked by another user.<br />
<br />
Some PDA devices would report errors on access to files on the removeable<br />
memory card if the PDA had powered down while the file was open.<br />
<br />
*2.8-8<br />
Relational operators in correlatives were not implying use of the reuse option.<br />
<br />
The C operation in F-correlatives did not handle negative numbers.<br />
<br />
Format codes applied to integer numeric values when non-default NLS delimiters<br />
were selected returned an incorrect result.<br />
<br />
The SET.FILE command did not handle multi-files correctly.<br />
<br />
Use of the NEXT qualifer to SETPTR or SET.QUEUE could cause QM to terminate<br />
abnormally on subsequent use of the CAPTURING clause to EXECUTE.<br />
<br />
The QMBasic CLEAR statement caused updates to subroutine argument variables<br />
that were passed by reference not to be treated as though they were passed by<br />
value, not returning the new value to the calling program.<br />
<br />
<strike>The QMBasic SUM() and SUMMATION() functions should ignore non-numeric elements<br />
in the dynamic array that they are summing.</strike><br />
*2.8-7<br />
Deleting a record from a file that used record level encryption could fail to<br />
remove the record from an alternate key index.<br />
<br />
The SED editor hung when trying to delete a record via the explore buffer if<br />
that record was locked by another user.<br />
<br />
The query processor treated Fn field references as being single valued.<br />
<br />
Reference to a dimensioned matrix on a QMBasic source line above the<br />
corresponding DIM statement generated a compilation error.<br />
<br />
A performance optimisation in the QMBasic LOCATE statement could result in the<br />
incorrect field position being returned or a QM fatal error. Also, LOCATE could<br />
incorrectly report an item as found if the leading characters matched the final<br />
item in the dynamci array being searched.<br />
*2.8-6<br />
The installer on some Linux systems could fail to set permissions correctly.<br />
<br />
There was an assumption that $HOLD was always in its default location.<br />
<br />
FORMAT was creating a VOC record named X.<br />
*2.8-5<br />
The init.d scripts on Linux and FreeBSD did not allow for installation with the<br />
QMSYS directory in a non-default location.<br />
<br />
The -R option of qmfix could report that the file was unusable.<br />
*2.8-4<br />
A direct network connection to QM using ports 4242 (telnet) or 4243 (QMClient)<br />
would fail on some versions of the network management software used by Linux<br />
and the PowerPC version of the Mac.<br />
<br />
Attempting to open a file that uses record level encryption was causing an<br />
abort for users with no access to the encryption key. This should have taken<br />
the ELSE clause of the open.<br />
<br />
FILE.SAVE was ignoring any account name given on the command line and saving<br />
all accounts.<br />
<br />
Using SEL.RESTORE to restore the VOC needed the file name to be entered as<br />
VOC-RESTORE. <br />
<br />
A QMBasic source line that generate a very large volume of object code could<br />
result in the program terminating unexpectedly.<br />
<br />
AccuSoft have supplied a correction to the terminfo definition for F5 in the<br />
vt100-at, vt220-at, vt320-at and vt420-at terminal types.<br />
*2.8-3<br />
Attempting to access a hashed file for which a user was locked out by file<br />
permissions could appear to open it as a directory file though it would not be<br />
possible to read or write records.<br />
<br />
Creating an alternate key index with an I-type, C-type or correlative that<br />
compiles to more than 512 bytes caused QM to terminate with a fatal error and<br />
left the index file corrupt.<br />
<br />
QM could terminate with a fatal error if a command executed using OS.EXECUTE<br />
with the CAPTURING clause returned only a newline.<br />
<br />
Use of an invalid pathname with the QMBasic OSWRITE statement did not take the<br />
ON ERROR clause.<br />
*2.8-2<br />
The ANALYSE.FILE command could wrongly report a file as having resizing<br />
disabled when it did not, or vice versa.<br />
<br />
The CREATE.INDEX and MAKE.INDEX commands did not always correctly recognise<br />
equivalent indices, resulting an an extra index being created where another<br />
that already existed could be used instead.<br />
<br />
Deleting all lines below the current position in ED and then saving the item<br />
could sometimes add a blank line to the end of the data.<br />
<br />
The query processor did not apply CSV quoting rules to column headings when<br />
creating comma separated output. <br />
<br />
A QMBasic class module with more than 255 entry points would appear to compile<br />
correctly but would produce run time errors.<br />
<br />
The QMBasic READCSV statement could cause a fatal error that terminated the<br />
QM session. <br />
<br />
A QMBasic class module in which a public function or subroutine aborted and the<br />
destructor routine then also aborted did not clean up correctly from the first<br />
abort.<br />
*2.8-1<br />
ACCOUNT.RESTORE could restore data to an incorrectly formed file name.<br />
<br />
The query processor BY.EXP.DSND operator was sorting in ascending order.<br />
*2.7-1<br />
The account restore tools did not handle filenames containing illegal<br />
characters correctly.<br />
*2.6-14<br />
The VOC $RELEASE record command editor control flags (field 3) were lost when<br />
installing a new release.<br />
<br />
The CODEPAGE option of the PTERM command was rejected.<br />
<br />
The QMBasic compiler could report an error if an include item had the same name<br />
as an equated token.<br />
*2.6-13<br />
A QMBasic indirect call where the indirection variable as an equated token<br />
failed to compile correctly.<br />
<br />
A QMBasic expression containing a Pick style implicit format element could<br />
sometimes be interpreted as a dimensioned matrix reference.<br />
<br />
The MT conversion code was returning 00:00 for a null input value.<br />
*2.6-12<br />
<strike>The FORMAT command reported an internal data mismatch if the program being<br />
formatted started with a blank line.</strike><br />
<br />
The QMBasic SELECTV statement generated a run time error if the source and<br />
target variables were the same.<br />
<br />
SELECTV "" TO VAR created a list with a single item named "__". <strong>--Unable to replicate. Need source code example--</strong><br />
<br />
The mc4 and mc5 terminfo keys were incorrect for some AccuTerm terminal types<br />
causing use of auxiliary port printing to display the data at the same time as<br />
it was printed. Also, pagination prompts could appear while the data was sent<br />
to the terminal.<br />
<br />
The QMCall() function of the qmclilib library on PPC Mac systems did not<br />
update returned argument values correctly.<br />
*2.6-11<br />
Use of an equate token that matched the alphabetic part of an @-variable name<br />
caused compilation errors. <strong>--Unable to replicate. Need source code example--</strong><br />
<br />
A null string in the data supplied to the !SORT() subroutine could cause QM<br />
to crash.<br />
*2.6-10<br />
Phantom processes failed to start when launched from sessions logged in as<br />
specific user numbers by use of the PORTMAP configuration parameter.<br />
<br />
The Hot Spot Monitor (HSM) did not count direct calls correctly.<br />
<br />
QMBasic programs accepted a string containing only a period as being a valid<br />
number and treated it as zero.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=List_of_fixed_bugs_in_the_commercial_version_of_OpenQM_(Current_as_of_2.8-10)&diff=372List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)2009-04-16T03:37:53Z<p>Glenb: </p>
<hr />
<div>The list of fixed issues below are in reverse version order. If one is fixed, please use the <nowiki><strike></strike></nowiki> html command to block out the fixed bug.<br />
<br />
*2.8-10<br />
The QMBasic compiler allowed use of EQ as an alternative to the = symbol as an<br />
assignment operator.<br />
<br />
Query commands that used closed range tests (e.g. A > 5 and < 8) with fields<br />
for which an alternate key index was present could return incorrect data.<br />
<br />
*2.8-9<br />
The N() funcion in an A-correlative did not allow for field names that did not<br />
comply with QM's naming rules.<br />
<br />
Where a file had multiple alternate key indices, if an index was built from a<br />
calculated value that used a T-conversion or a TRANS() function to reference a<br />
record that did not exist, all later index updates for the same write would<br />
damage the index.<br />
<br />
Use of PSTAT could cause the process being queried to crash if it had a very<br />
deep execution stack or was executing a very long command. <br />
<br />
A phantom would fail to start correctly if the parent process terminated before<br />
it had commenced its initialisation.<br />
<br />
The Proc A command did not treat semicolons in the source data as a special<br />
character separating multiple items.<br />
<br />
A Proc with a command of H with no qualifying text caused the Proc processor<br />
to loop.<br />
<br />
The LPTR keyword was not recognised by the FILE.STAT command.<br />
<br />
The WHEN clause of the query processor was not handling some complex conditions<br />
correctly.<br />
<br />
A Pick style qualified display clause on a multivalued field was equivalent to<br />
use of WITH when it should have been equivalent to use of WHEN.<br />
<br />
Quitting out of a PSTAT command could result in not being able to start pahntom<br />
processes.<br />
<br />
<strike>The @FILENAME synonym for @FILE.NAME was not recognised by the QMBasic<br />
compiler.</strike><br />
<br />
The QMBasic OPENSEQ statement did not return the blocking user number via the<br />
STATUS() function if the record was locked by another user.<br />
<br />
Some PDA devices would report errors on access to files on the removeable<br />
memory card if the PDA had powered down while the file was open.<br />
<br />
*2.8-8<br />
Relational operators in correlatives were not implying use of the reuse option.<br />
<br />
The C operation in F-correlatives did not handle negative numbers.<br />
<br />
Format codes applied to integer numeric values when non-default NLS delimiters<br />
were selected returned an incorrect result.<br />
<br />
The SET.FILE command did not handle multi-files correctly.<br />
<br />
Use of the NEXT qualifer to SETPTR or SET.QUEUE could cause QM to terminate<br />
abnormally on subsequent use of the CAPTURING clause to EXECUTE.<br />
<br />
The QMBasic CLEAR statement caused updates to subroutine argument variables<br />
that were passed by reference not to be treated as though they were passed by<br />
value, not returning the new value to the calling program.<br />
<br />
<strike>The QMBasic SUM() and SUMMATION() functions should ignore non-numeric elements<br />
in the dynamic array that they are summing.</strike><br />
*2.8-7<br />
Deleting a record from a file that used record level encryption could fail to<br />
remove the record from an alternate key index.<br />
<br />
The SED editor hung when trying to delete a record via the explore buffer if<br />
that record was locked by another user.<br />
<br />
The query processor treated Fn field references as being single valued.<br />
<br />
Reference to a dimensioned matrix on a QMBasic source line above the<br />
corresponding DIM statement generated a compilation error.<br />
<br />
A performance optimisation in the QMBasic LOCATE statement could result in the<br />
incorrect field position being returned or a QM fatal error. Also, LOCATE could<br />
incorrectly report an item as found if the leading characters matched the final<br />
item in the dynamci array being searched.<br />
*2.8-6<br />
The installer on some Linux systems could fail to set permissions correctly.<br />
<br />
There was an assumption that $HOLD was always in its default location.<br />
<br />
FORMAT was creating a VOC record named X.<br />
*2.8-5<br />
The init.d scripts on Linux and FreeBSD did not allow for installation with the<br />
QMSYS directory in a non-default location.<br />
<br />
The -R option of qmfix could report that the file was unusable.<br />
*2.8-4<br />
A direct network connection to QM using ports 4242 (telnet) or 4243 (QMClient)<br />
would fail on some versions of the network management software used by Linux<br />
and the PowerPC version of the Mac.<br />
<br />
Attempting to open a file that uses record level encryption was causing an<br />
abort for users with no access to the encryption key. This should have taken<br />
the ELSE clause of the open.<br />
<br />
FILE.SAVE was ignoring any account name given on the command line and saving<br />
all accounts.<br />
<br />
Using SEL.RESTORE to restore the VOC needed the file name to be entered as<br />
VOC-RESTORE. <br />
<br />
A QMBasic source line that generate a very large volume of object code could<br />
result in the program terminating unexpectedly.<br />
<br />
AccuSoft have supplied a correction to the terminfo definition for F5 in the<br />
vt100-at, vt220-at, vt320-at and vt420-at terminal types.<br />
*2.8-3<br />
Attempting to access a hashed file for which a user was locked out by file<br />
permissions could appear to open it as a directory file though it would not be<br />
possible to read or write records.<br />
<br />
Creating an alternate key index with an I-type, C-type or correlative that<br />
compiles to more than 512 bytes caused QM to terminate with a fatal error and<br />
left the index file corrupt.<br />
<br />
QM could terminate with a fatal error if a command executed using OS.EXECUTE<br />
with the CAPTURING clause returned only a newline.<br />
<br />
Use of an invalid pathname with the QMBasic OSWRITE statement did not take the<br />
ON ERROR clause.<br />
*2.8-2<br />
The ANALYSE.FILE command could wrongly report a file as having resizing<br />
disabled when it did not, or vice versa.<br />
<br />
The CREATE.INDEX and MAKE.INDEX commands did not always correctly recognise<br />
equivalent indices, resulting an an extra index being created where another<br />
that already existed could be used instead.<br />
<br />
Deleting all lines below the current position in ED and then saving the item<br />
could sometimes add a blank line to the end of the data.<br />
<br />
The query processor did not apply CSV quoting rules to column headings when<br />
creating comma separated output. <br />
<br />
A QMBasic class module with more than 255 entry points would appear to compile<br />
correctly but would produce run time errors.<br />
<br />
The QMBasic READCSV statement could cause a fatal error that terminated the<br />
QM session. <br />
<br />
A QMBasic class module in which a public function or subroutine aborted and the<br />
destructor routine then also aborted did not clean up correctly from the first<br />
abort.<br />
*2.8-1<br />
ACCOUNT.RESTORE could restore data to an incorrectly formed file name.<br />
<br />
The query processor BY.EXP.DSND operator was sorting in ascending order.<br />
*2.7-1<br />
The account restore tools did not handle filenames containing illegal<br />
characters correctly.<br />
*2.6-14<br />
The VOC $RELEASE record command editor control flags (field 3) were lost when<br />
installing a new release.<br />
<br />
The CODEPAGE option of the PTERM command was rejected.<br />
<br />
The QMBasic compiler could report an error if an include item had the same name<br />
as an equated token.<br />
*2.6-13<br />
A QMBasic indirect call where the indirection variable as an equated token<br />
failed to compile correctly.<br />
<br />
A QMBasic expression containing a Pick style implicit format element could<br />
sometimes be interpreted as a dimensioned matrix reference.<br />
<br />
The MT conversion code was returning 00:00 for a null input value.<br />
*2.6-12<br />
<strike>The FORMAT command reported an internal data mismatch if the program being<br />
formatted started with a blank line.</strike><br />
<br />
The QMBasic SELECTV statement generated a run time error if the source and<br />
target variables were the same.<br />
<br />
SELECTV "" TO VAR created a list with a single item named "__".<br />
<br />
The mc4 and mc5 terminfo keys were incorrect for some AccuTerm terminal types<br />
causing use of auxiliary port printing to display the data at the same time as<br />
it was printed. Also, pagination prompts could appear while the data was sent<br />
to the terminal.<br />
<br />
The QMCall() function of the qmclilib library on PPC Mac systems did not<br />
update returned argument values correctly.<br />
*2.6-11<br />
Use of an equate token that matched the alphabetic part of an @-variable name<br />
caused compilation errors. <strong>--Unable to replicate. Need source code example--</strong><br />
<br />
A null string in the data supplied to the !SORT() subroutine could cause QM<br />
to crash.<br />
*2.6-10<br />
Phantom processes failed to start when launched from sessions logged in as<br />
specific user numbers by use of the PORTMAP configuration parameter.<br />
<br />
The Hot Spot Monitor (HSM) did not count direct calls correctly.<br />
<br />
QMBasic programs accepted a string containing only a period as being a valid<br />
number and treated it as zero.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=List_of_fixed_bugs_in_the_commercial_version_of_OpenQM_(Current_as_of_2.8-10)&diff=371List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)2009-04-15T03:43:19Z<p>Glenb: </p>
<hr />
<div>The list of fixed issues below are in reverse version order. If one is fixed, please use the <nowiki><strike></strike></nowiki> html command to block out the fixed bug.<br />
<br />
*2.8-10<br />
The QMBasic compiler allowed use of EQ as an alternative to the = symbol as an<br />
assignment operator.<br />
<br />
Query commands that used closed range tests (e.g. A > 5 and < 8) with fields<br />
for which an alternate key index was present could return incorrect data.<br />
<br />
*2.8-9<br />
The N() funcion in an A-correlative did not allow for field names that did not<br />
comply with QM's naming rules.<br />
<br />
Where a file had multiple alternate key indices, if an index was built from a<br />
calculated value that used a T-conversion or a TRANS() function to reference a<br />
record that did not exist, all later index updates for the same write would<br />
damage the index.<br />
<br />
Use of PSTAT could cause the process being queried to crash if it had a very<br />
deep execution stack or was executing a very long command. <br />
<br />
A phantom would fail to start correctly if the parent process terminated before<br />
it had commenced its initialisation.<br />
<br />
The Proc A command did not treat semicolons in the source data as a special<br />
character separating multiple items.<br />
<br />
A Proc with a command of H with no qualifying text caused the Proc processor<br />
to loop.<br />
<br />
The LPTR keyword was not recognised by the FILE.STAT command.<br />
<br />
The WHEN clause of the query processor was not handling some complex conditions<br />
correctly.<br />
<br />
A Pick style qualified display clause on a multivalued field was equivalent to<br />
use of WITH when it should have been equivalent to use of WHEN.<br />
<br />
Quitting out of a PSTAT command could result in not being able to start pahntom<br />
processes.<br />
<br />
<strike>The @FILENAME synonym for @FILE.NAME was not recognised by the QMBasic<br />
compiler.</strike><br />
<br />
The QMBasic OPENSEQ statement did not return the blocking user number via the<br />
STATUS() function if the record was locked by another user.<br />
<br />
Some PDA devices would report errors on access to files on the removeable<br />
memory card if the PDA had powered down while the file was open.<br />
<br />
*2.8-8<br />
Relational operators in correlatives were not implying use of the reuse option.<br />
<br />
The C operation in F-correlatives did not handle negative numbers.<br />
<br />
Format codes applied to integer numeric values when non-default NLS delimiters<br />
were selected returned an incorrect result.<br />
<br />
The SET.FILE command did not handle multi-files correctly.<br />
<br />
Use of the NEXT qualifer to SETPTR or SET.QUEUE could cause QM to terminate<br />
abnormally on subsequent use of the CAPTURING clause to EXECUTE.<br />
<br />
The QMBasic CLEAR statement caused updates to subroutine argument variables<br />
that were passed by reference not to be treated as though they were passed by<br />
value, not returning the new value to the calling program.<br />
<br />
<strike>The QMBasic SUM() and SUMMATION() functions should ignore non-numeric elements<br />
in the dynamic array that they are summing.</strike><br />
*2.8-7<br />
Deleting a record from a file that used record level encryption could fail to<br />
remove the record from an alternate key index.<br />
<br />
The SED editor hung when trying to delete a record via the explore buffer if<br />
that record was locked by another user.<br />
<br />
The query processor treated Fn field references as being single valued.<br />
<br />
Reference to a dimensioned matrix on a QMBasic source line above the<br />
corresponding DIM statement generated a compilation error.<br />
<br />
A performance optimisation in the QMBasic LOCATE statement could result in the<br />
incorrect field position being returned or a QM fatal error. Also, LOCATE could<br />
incorrectly report an item as found if the leading characters matched the final<br />
item in the dynamci array being searched.<br />
*2.8-6<br />
The installer on some Linux systems could fail to set permissions correctly.<br />
<br />
There was an assumption that $HOLD was always in its default location.<br />
<br />
FORMAT was creating a VOC record named X.<br />
*2.8-5<br />
The init.d scripts on Linux and FreeBSD did not allow for installation with the<br />
QMSYS directory in a non-default location.<br />
<br />
The -R option of qmfix could report that the file was unusable.<br />
*2.8-4<br />
A direct network connection to QM using ports 4242 (telnet) or 4243 (QMClient)<br />
would fail on some versions of the network management software used by Linux<br />
and the PowerPC version of the Mac.<br />
<br />
Attempting to open a file that uses record level encryption was causing an<br />
abort for users with no access to the encryption key. This should have taken<br />
the ELSE clause of the open.<br />
<br />
FILE.SAVE was ignoring any account name given on the command line and saving<br />
all accounts.<br />
<br />
Using SEL.RESTORE to restore the VOC needed the file name to be entered as<br />
VOC-RESTORE. <br />
<br />
A QMBasic source line that generate a very large volume of object code could<br />
result in the program terminating unexpectedly.<br />
<br />
AccuSoft have supplied a correction to the terminfo definition for F5 in the<br />
vt100-at, vt220-at, vt320-at and vt420-at terminal types.<br />
*2.8-3<br />
Attempting to access a hashed file for which a user was locked out by file<br />
permissions could appear to open it as a directory file though it would not be<br />
possible to read or write records.<br />
<br />
Creating an alternate key index with an I-type, C-type or correlative that<br />
compiles to more than 512 bytes caused QM to terminate with a fatal error and<br />
left the index file corrupt.<br />
<br />
QM could terminate with a fatal error if a command executed using OS.EXECUTE<br />
with the CAPTURING clause returned only a newline.<br />
<br />
Use of an invalid pathname with the QMBasic OSWRITE statement did not take the<br />
ON ERROR clause.<br />
*2.8-2<br />
The ANALYSE.FILE command could wrongly report a file as having resizing<br />
disabled when it did not, or vice versa.<br />
<br />
The CREATE.INDEX and MAKE.INDEX commands did not always correctly recognise<br />
equivalent indices, resulting an an extra index being created where another<br />
that already existed could be used instead.<br />
<br />
Deleting all lines below the current position in ED and then saving the item<br />
could sometimes add a blank line to the end of the data.<br />
<br />
The query processor did not apply CSV quoting rules to column headings when<br />
creating comma separated output. <br />
<br />
A QMBasic class module with more than 255 entry points would appear to compile<br />
correctly but would produce run time errors.<br />
<br />
The QMBasic READCSV statement could cause a fatal error that terminated the<br />
QM session. <br />
<br />
A QMBasic class module in which a public function or subroutine aborted and the<br />
destructor routine then also aborted did not clean up correctly from the first<br />
abort.<br />
*2.8-1<br />
ACCOUNT.RESTORE could restore data to an incorrectly formed file name.<br />
<br />
The query processor BY.EXP.DSND operator was sorting in ascending order.<br />
*2.7-1<br />
The account restore tools did not handle filenames containing illegal<br />
characters correctly.<br />
*2.6-14<br />
The VOC $RELEASE record command editor control flags (field 3) were lost when<br />
installing a new release.<br />
<br />
The CODEPAGE option of the PTERM command was rejected.<br />
<br />
The QMBasic compiler could report an error if an include item had the same name<br />
as an equated token.<br />
*2.6-13<br />
A QMBasic indirect call where the indirection variable as an equated token<br />
failed to compile correctly.<br />
<br />
A QMBasic expression containing a Pick style implicit format element could<br />
sometimes be interpreted as a dimensioned matrix reference.<br />
<br />
The MT conversion code was returning 00:00 for a null input value.<br />
*2.6-12<br />
<strike>The FORMAT command reported an internal data mismatch if the program being<br />
formatted started with a blank line.</strike><br />
<br />
The QMBasic SELECTV statement generated a run time error if the source and<br />
target variables were the same.<br />
<br />
SELECTV "" TO VAR created a list with a single item named "__".<br />
<br />
The mc4 and mc5 terminfo keys were incorrect for some AccuTerm terminal types<br />
causing use of auxiliary port printing to display the data at the same time as<br />
it was printed. Also, pagination prompts could appear while the data was sent<br />
to the terminal.<br />
<br />
The QMCall() function of the qmclilib library on PPC Mac systems did not<br />
update returned argument values correctly.<br />
*2.6-11<br />
Use of an equate token that matched the alphabetic part of an @-variable name<br />
caused compilation errors.<br />
<br />
A null string in the data supplied to the !SORT() subroutine could cause QM<br />
to crash.<br />
*2.6-10<br />
Phantom processes failed to start when launched from sessions logged in as<br />
specific user numbers by use of the PORTMAP configuration parameter.<br />
<br />
The Hot Spot Monitor (HSM) did not count direct calls correctly.<br />
<br />
QMBasic programs accepted a string containing only a period as being a valid<br />
number and treated it as zero.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=List_of_fixed_bugs_in_the_commercial_version_of_OpenQM_(Current_as_of_2.8-10)&diff=370List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)2009-04-15T03:42:39Z<p>Glenb: </p>
<hr />
<div>The list of fixed issues below are in reverse version order. If one is fixed, please use the <nowiki><strike></strike></nowiki> html command to block out the fixed bug.<br />
<br />
*2.8-10<br />
The QMBasic compiler allowed use of EQ as an alternative to the = symbol as an<br />
assignment operator.<br />
<br />
Query commands that used closed range tests (e.g. A > 5 and < 8) with fields<br />
for which an alternate key index was present could return incorrect data.<br />
<br />
*2.8-9<br />
The N() funcion in an A-correlative did not allow for field names that did not<br />
comply with QM's naming rules.<br />
<br />
Where a file had multiple alternate key indices, if an index was built from a<br />
calculated value that used a T-conversion or a TRANS() function to reference a<br />
record that did not exist, all later index updates for the same write would<br />
damage the index.<br />
<br />
Use of PSTAT could cause the process being queried to crash if it had a very<br />
deep execution stack or was executing a very long command. <br />
<br />
A phantom would fail to start correctly if the parent process terminated before<br />
it had commenced its initialisation.<br />
<br />
The Proc A command did not treat semicolons in the source data as a special<br />
character separating multiple items.<br />
<br />
A Proc with a command of H with no qualifying text caused the Proc processor<br />
to loop.<br />
<br />
The LPTR keyword was not recognised by the FILE.STAT command.<br />
<br />
The WHEN clause of the query processor was not handling some complex conditions<br />
correctly.<br />
<br />
A Pick style qualified display clause on a multivalued field was equivalent to<br />
use of WITH when it should have been equivalent to use of WHEN.<br />
<br />
Quitting out of a PSTAT command could result in not being able to start pahntom<br />
processes.<br />
<br />
<strike>The @FILENAME synonym for @FILE.NAME was not recognised by the QMBasic<br />
compiler.</strike><br />
<br />
The QMBasic OPENSEQ statement did not return the blocking user number via the<br />
STATUS() function if the record was locked by another user.<br />
<br />
Some PDA devices would report errors on access to files on the removeable<br />
memory card if the PDA had powered down while the file was open.<br />
<br />
*2.8-8<br />
Relational operators in correlatives were not implying use of the reuse option.<br />
<br />
The C operation in F-correlatives did not handle negative numbers.<br />
<br />
Format codes applied to integer numeric values when non-default NLS delimiters<br />
were selected returned an incorrect result.<br />
<br />
The SET.FILE command did not handle multi-files correctly.<br />
<br />
Use of the NEXT qualifer to SETPTR or SET.QUEUE could cause QM to terminate<br />
abnormally on subsequent use of the CAPTURING clause to EXECUTE.<br />
<br />
The QMBasic CLEAR statement caused updates to subroutine argument variables<br />
that were passed by reference not to be treated as though they were passed by<br />
value, not returning the new value to the calling program.<br />
<br />
<strike>The QMBasic SUM() and SUMMATION() functions should ignore non-numeric elements<br />
in the dynamic array that they are summing.</strike><br />
*2.8-7<br />
Deleting a record from a file that used record level encryption could fail to<br />
remove the record from an alternate key index.<br />
<br />
The SED editor hung when trying to delete a record via the explore buffer if<br />
that record was locked by another user.<br />
<br />
The query processor treated Fn field references as being single valued.<br />
<br />
Reference to a dimensioned matrix on a QMBasic source line above the<br />
corresponding DIM statement generated a compilation error.<br />
<br />
A performance optimisation in the QMBasic LOCATE statement could result in the<br />
incorrect field position being returned or a QM fatal error. Also, LOCATE could<br />
incorrectly report an item as found if the leading characters matched the final<br />
item in the dynamci array being searched.<br />
*2.8-6<br />
The installer on some Linux systems could fail to set permissions correctly.<br />
<br />
There was an assumption that $HOLD was always in its default location.<br />
<br />
FORMAT was creating a VOC record named X.<br />
*2.8-5<br />
The init.d scripts on Linux and FreeBSD did not allow for installation with the<br />
QMSYS directory in a non-default location.<br />
<br />
The -R option of qmfix could report that the file was unusable.<br />
*2.8-4<br />
A direct network connection to QM using ports 4242 (telnet) or 4243 (QMClient)<br />
would fail on some versions of the network management software used by Linux<br />
and the PowerPC version of the Mac.<br />
<br />
Attempting to open a file that uses record level encryption was causing an<br />
abort for users with no access to the encryption key. This should have taken<br />
the ELSE clause of the open.<br />
<br />
FILE.SAVE was ignoring any account name given on the command line and saving<br />
all accounts.<br />
<br />
Using SEL.RESTORE to restore the VOC needed the file name to be entered as<br />
VOC-RESTORE. <br />
<br />
A QMBasic source line that generate a very large volume of object code could<br />
result in the program terminating unexpectedly.<br />
<br />
AccuSoft have supplied a correction to the terminfo definition for F5 in the<br />
vt100-at, vt220-at, vt320-at and vt420-at terminal types.<br />
*2.8-3<br />
Attempting to access a hashed file for which a user was locked out by file<br />
permissions could appear to open it as a directory file though it would not be<br />
possible to read or write records.<br />
<br />
Creating an alternate key index with an I-type, C-type or correlative that<br />
compiles to more than 512 bytes caused QM to terminate with a fatal error and<br />
left the index file corrupt.<br />
<br />
QM could terminate with a fatal error if a command executed using OS.EXECUTE<br />
with the CAPTURING clause returned only a newline.<br />
<br />
Use of an invalid pathname with the QMBasic OSWRITE statement did not take the<br />
ON ERROR clause.<br />
*2.8-2<br />
The ANALYSE.FILE command could wrongly report a file as having resizing<br />
disabled when it did not, or vice versa.<br />
<br />
The CREATE.INDEX and MAKE.INDEX commands did not always correctly recognise<br />
equivalent indices, resulting an an extra index being created where another<br />
that already existed could be used instead.<br />
<br />
Deleting all lines below the current position in ED and then saving the item<br />
could sometimes add a blank line to the end of the data.<br />
<br />
The query processor did not apply CSV quoting rules to column headings when<br />
creating comma separated output. <br />
<br />
A QMBasic class module with more than 255 entry points would appear to compile<br />
correctly but would produce run time errors.<br />
<br />
The QMBasic READCSV statement could cause a fatal error that terminated the<br />
QM session. <br />
<br />
A QMBasic class module in which a public function or subroutine aborted and the<br />
destructor routine then also aborted did not clean up correctly from the first<br />
abort.<br />
*2.8-1<br />
ACCOUNT.RESTORE could restore data to an incorrectly formed file name.<br />
<br />
The query processor BY.EXP.DSND operator was sorting in ascending order.<br />
*2.7-1<br />
The account restore tools did not handle filenames containing illegal<br />
characters correctly.<br />
*2.6-14<br />
The VOC $RELEASE record command editor control flags (field 3) were lost when<br />
installing a new release.<br />
<br />
The CODEPAGE option of the PTERM command was rejected.<br />
<br />
The QMBasic compiler could report an error if an include item had the same name<br />
as an equated token.<br />
*2.6-13<br />
A QMBasic indirect call where the indirection variable as an equated token<br />
failed to compile correctly.<br />
<br />
A QMBasic expression containing a Pick style implicit format element could<br />
sometimes be interpreted as a dimensioned matrix reference.<br />
<br />
The MT conversion code was returning 00:00 for a null input value.<br />
*2.6-12<br />
<strike>The FORMAT command reported an internal data mismatch if the program being<br />
formatted started with a blank line.</strike><br />
<br />
The QMBasic SELECTV statement generated a run time error if the source and<br />
target variables were the same.<br />
<br />
SELECTV "" TO VAR created a list with a single item named "__".<br />
<br />
The mc4 and mc5 terminfo keys were incorrect for some AccuTerm terminal types<br />
causing use of auxiliary port printing to display the data at the same time as<br />
it was printed. Also, pagination prompts could appear while the data was sent<br />
to the terminal.<br />
<br />
The QMCall() function of the qmclilib library on PPC Mac systems did not<br />
update returned argument values correctly.<br />
*2.6-11<br />
Use of an equate token that matched the alphabetic part of an @-variable name<br />
caused compilation errors.<br />
<br />
A null string in the data supplied to the !SORT() subroutine could cause QM<br />
to crash.<br />
*2.6-10<br />
Phantom processes failed to start when launched from sessions logged in as<br />
specific user numbers by use of the PORTMAP configuration parameter.<br />
<br />
The Hot Spot Monitor (HSM) did not count direct calls correctly.<br />
<br />
QMBasic programs accepted a string containing only a period as being a valid<br />
number and treated it as zero.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=List_of_fixed_bugs_in_the_commercial_version_of_OpenQM_(Current_as_of_2.8-10)&diff=369List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)2009-04-15T03:36:11Z<p>Glenb: </p>
<hr />
<div>The list of fixed issues below are in reverse version order. If one is fixed, please use the <nowiki><strike></strike></nowiki> html command to block out the fixed bug.<br />
<br />
*2.8-10<br />
The QMBasic compiler allowed use of EQ as an alternative to the = symbol as an<br />
assignment operator.<br />
<br />
Query commands that used closed range tests (e.g. A > 5 and < 8) with fields<br />
for which an alternate key index was present could return incorrect data.<br />
<br />
*2.8-9<br />
The N() funcion in an A-correlative did not allow for field names that did not<br />
comply with QM's naming rules.<br />
<br />
Where a file had multiple alternate key indices, if an index was built from a<br />
calculated value that used a T-conversion or a TRANS() function to reference a<br />
record that did not exist, all later index updates for the same write would<br />
damage the index.<br />
<br />
Use of PSTAT could cause the process being queried to crash if it had a very<br />
deep execution stack or was executing a very long command. <br />
<br />
A phantom would fail to start correctly if the parent process terminated before<br />
it had commenced its initialisation.<br />
<br />
The Proc A command did not treat semicolons in the source data as a special<br />
character separating multiple items.<br />
<br />
A Proc with a command of H with no qualifying text caused the Proc processor<br />
to loop.<br />
<br />
The LPTR keyword was not recognised by the FILE.STAT command.<br />
<br />
The WHEN clause of the query processor was not handling some complex conditions<br />
correctly.<br />
<br />
A Pick style qualified display clause on a multivalued field was equivalent to<br />
use of WITH when it should have been equivalent to use of WHEN.<br />
<br />
Quitting out of a PSTAT command could result in not being able to start pahntom<br />
processes.<br />
<br />
<strike> The @FILENAME synonym for @FILE.NAME was not recognised by the QMBasic<br />
compiler. </strike><br />
<br />
The QMBasic OPENSEQ statement did not return the blocking user number via the<br />
STATUS() function if the record was locked by another user.<br />
<br />
Some PDA devices would report errors on access to files on the removeable<br />
memory card if the PDA had powered down while the file was open.<br />
<br />
*2.8-8<br />
Relational operators in correlatives were not implying use of the reuse option.<br />
<br />
The C operation in F-correlatives did not handle negative numbers.<br />
<br />
Format codes applied to integer numeric values when non-default NLS delimiters<br />
were selected returned an incorrect result.<br />
<br />
The SET.FILE command did not handle multi-files correctly.<br />
<br />
Use of the NEXT qualifer to SETPTR or SET.QUEUE could cause QM to terminate<br />
abnormally on subsequent use of the CAPTURING clause to EXECUTE.<br />
<br />
The QMBasic CLEAR statement caused updates to subroutine argument variables<br />
that were passed by reference not to be treated as though they were passed by<br />
value, not returning the new value to the calling program.<br />
<br />
The QMBasic SUM() and SUMMATION() functions should ignore non-numeric elements<br />
in the dynamic array that they are summing.<br />
*2.8-7<br />
Deleting a record from a file that used record level encryption could fail to<br />
remove the record from an alternate key index.<br />
<br />
The SED editor hung when trying to delete a record via the explore buffer if<br />
that record was locked by another user.<br />
<br />
The query processor treated Fn field references as being single valued.<br />
<br />
Reference to a dimensioned matrix on a QMBasic source line above the<br />
corresponding DIM statement generated a compilation error.<br />
<br />
A performance optimisation in the QMBasic LOCATE statement could result in the<br />
incorrect field position being returned or a QM fatal error. Also, LOCATE could<br />
incorrectly report an item as found if the leading characters matched the final<br />
item in the dynamci array being searched.<br />
*2.8-6<br />
The installer on some Linux systems could fail to set permissions correctly.<br />
<br />
There was an assumption that $HOLD was always in its default location.<br />
<br />
FORMAT was creating a VOC record named X.<br />
*2.8-5<br />
The init.d scripts on Linux and FreeBSD did not allow for installation with the<br />
QMSYS directory in a non-default location.<br />
<br />
The -R option of qmfix could report that the file was unusable.<br />
*2.8-4<br />
A direct network connection to QM using ports 4242 (telnet) or 4243 (QMClient)<br />
would fail on some versions of the network management software used by Linux<br />
and the PowerPC version of the Mac.<br />
<br />
Attempting to open a file that uses record level encryption was causing an<br />
abort for users with no access to the encryption key. This should have taken<br />
the ELSE clause of the open.<br />
<br />
FILE.SAVE was ignoring any account name given on the command line and saving<br />
all accounts.<br />
<br />
Using SEL.RESTORE to restore the VOC needed the file name to be entered as<br />
VOC-RESTORE. <br />
<br />
A QMBasic source line that generate a very large volume of object code could<br />
result in the program terminating unexpectedly.<br />
<br />
AccuSoft have supplied a correction to the terminfo definition for F5 in the<br />
vt100-at, vt220-at, vt320-at and vt420-at terminal types.<br />
*2.8-3<br />
Attempting to access a hashed file for which a user was locked out by file<br />
permissions could appear to open it as a directory file though it would not be<br />
possible to read or write records.<br />
<br />
Creating an alternate key index with an I-type, C-type or correlative that<br />
compiles to more than 512 bytes caused QM to terminate with a fatal error and<br />
left the index file corrupt.<br />
<br />
QM could terminate with a fatal error if a command executed using OS.EXECUTE<br />
with the CAPTURING clause returned only a newline.<br />
<br />
Use of an invalid pathname with the QMBasic OSWRITE statement did not take the<br />
ON ERROR clause.<br />
*2.8-2<br />
The ANALYSE.FILE command could wrongly report a file as having resizing<br />
disabled when it did not, or vice versa.<br />
<br />
The CREATE.INDEX and MAKE.INDEX commands did not always correctly recognise<br />
equivalent indices, resulting an an extra index being created where another<br />
that already existed could be used instead.<br />
<br />
Deleting all lines below the current position in ED and then saving the item<br />
could sometimes add a blank line to the end of the data.<br />
<br />
The query processor did not apply CSV quoting rules to column headings when<br />
creating comma separated output. <br />
<br />
A QMBasic class module with more than 255 entry points would appear to compile<br />
correctly but would produce run time errors.<br />
<br />
The QMBasic READCSV statement could cause a fatal error that terminated the<br />
QM session. <br />
<br />
A QMBasic class module in which a public function or subroutine aborted and the<br />
destructor routine then also aborted did not clean up correctly from the first<br />
abort.<br />
*2.8-1<br />
ACCOUNT.RESTORE could restore data to an incorrectly formed file name.<br />
<br />
The query processor BY.EXP.DSND operator was sorting in ascending order.<br />
*2.7-1<br />
The account restore tools did not handle filenames containing illegal<br />
characters correctly.<br />
*2.6-14<br />
The VOC $RELEASE record command editor control flags (field 3) were lost when<br />
installing a new release.<br />
<br />
The CODEPAGE option of the PTERM command was rejected.<br />
<br />
The QMBasic compiler could report an error if an include item had the same name<br />
as an equated token.<br />
*2.6-13<br />
A QMBasic indirect call where the indirection variable as an equated token<br />
failed to compile correctly.<br />
<br />
A QMBasic expression containing a Pick style implicit format element could<br />
sometimes be interpreted as a dimensioned matrix reference.<br />
<br />
The MT conversion code was returning 00:00 for a null input value.<br />
*2.6-12<br />
<strike>The FORMAT command reported an internal data mismatch if the program being<br />
formatted started with a blank line.</strike><br />
<br />
The QMBasic SELECTV statement generated a run time error if the source and<br />
target variables were the same.<br />
<br />
SELECTV "" TO VAR created a list with a single item named "__".<br />
<br />
The mc4 and mc5 terminfo keys were incorrect for some AccuTerm terminal types<br />
causing use of auxiliary port printing to display the data at the same time as<br />
it was printed. Also, pagination prompts could appear while the data was sent<br />
to the terminal.<br />
<br />
The QMCall() function of the qmclilib library on PPC Mac systems did not<br />
update returned argument values correctly.<br />
*2.6-11<br />
Use of an equate token that matched the alphabetic part of an @-variable name<br />
caused compilation errors.<br />
<br />
A null string in the data supplied to the !SORT() subroutine could cause QM<br />
to crash.<br />
*2.6-10<br />
Phantom processes failed to start when launched from sessions logged in as<br />
specific user numbers by use of the PORTMAP configuration parameter.<br />
<br />
The Hot Spot Monitor (HSM) did not count direct calls correctly.<br />
<br />
QMBasic programs accepted a string containing only a period as being a valid<br />
number and treated it as zero.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Main_Page&diff=350Main Page2009-04-11T20:20:28Z<p>Glenb: /* For Developers */</p>
<hr />
<div>gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br />
<br />
This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br />
<br />
Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br />
<br />
The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br />
<br />
'''This server is DOWN/SLOW around 04:00GMT nightly for 15mins while backing up.'''<br />
<br />
==For Users==<br />
*[[Downloads]]: Source tarball and package builds for key platforms<br />
*[[Guides & HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br />
*[[QMBASIC Enhancements]] - QMBASIC features that are custom or were not part of the original GPL release.<br />
*[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br />
*[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br />
*General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br />
*IRC Chat: irc://irc.efnet.org/openqm<br />
====Supporting Projects====<br />
Various external projects that provide tools for or API's into OpenQM<br />
* [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br />
*[[PHP_Native_API|PHP Native API module]]<br />
*[[C++ Wrapper]]<br />
*Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br />
* [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br />
<br />
==For Developers==<br />
For those that want to contribute to OpenQM GPL project.<br />
*Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br />
*Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br />
*[[Development snapshots]] - How to obtain, build, and upgrade using the snapshots.<br />
*[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br />
*[[Wish list]] - Things that you want & that we need contributors/devs for (lots of small things)<br />
*[[Dynamic linking]] - Calling objects written in other languages.<br />
*[[Installers]] - Installing scripts/programs or package systems<br />
<br />
== How do I use this site? ==<br />
<br />
If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br />
<br />
If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br />
<br />
While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br />
<br />
=== External Resources ===<br />
* [[Installations]] - Places where GPL OpenQM is in use (I'm attempting to create a new section for this) - http://capersqm.dnsalias.net/<br />
* [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br />
* [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module (C Wrapper) <br />
<br />
<br />
<br />
--[[Administration]]</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=349Custom Compiler Modes2009-04-08T02:17:32Z<p>Glenb: /* OpenQM GPL Custom Compiler Modes */</p>
<hr />
<div><br />
== OpenQM GPL Compatibility Compiler Modes ==<br />
<br />
'''HEADING.NO.EJECT''' - This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
<br />
'''NO.ECHO.DATA''' - This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
<br />
----<br />
<br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
'''NO.CASE.INVERT''' - This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=348Custom Compiler Modes2009-04-08T02:17:10Z<p>Glenb: /* OpenQM GPL Compatibility Compiler Modes */</p>
<hr />
<div><br />
== OpenQM GPL Compatibility Compiler Modes ==<br />
<br />
'''HEADING.NO.EJECT''' - This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
<br />
'''NO.ECHO.DATA''' - This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
'''NO.CASE.INVERT''' - This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=347Custom Compiler Modes2009-04-08T02:15:58Z<p>Glenb: /* OpenQM GPL Custom Compiler Modes */</p>
<hr />
<div><br />
== OpenQM GPL Compatibility Compiler Modes ==<br />
<br />
'''NO.ECHO.DATA''' - This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
'''HEADING.NO.EJECT''' - This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
<br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
'''NO.CASE.INVERT''' - This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_Compiler_Modes&diff=346Custom Compiler Modes2009-04-08T02:12:22Z<p>Glenb: </p>
<hr />
<div><br />
== OpenQM GPL Custom Compiler Modes ==<br />
<br />
'''NO.ECHO.DATA''' - This is provided to function the same as the commercial NO.ECHO.DATA. When this mode is enabled, the application will not echo characters to standard out/terminal when being used as a data input method.<br />
<br />
'''HEADING.NO.EJECT''' - This is provided to function the same as the commercial HEADING.NO.EJECT. When this mode is enabled, the NO.EJECT mode of the QMBasic HEADING statement is set as the default. Automatic page throw, on setting a new heading, is suppressed.<br />
<br />
'''NO.CASE.INVERT''' - This mode will cause INPUT and INPUT@ to ignore the case inversion state of PTERM, when the application executes. The state of PTERM is reserved during execution of _INPUT, so the session operates normally outside of the code which has "$mode no.case.invert" specified.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=345Custom QMBASIC Options2009-04-07T04:17:11Z<p>Glenb: /* QMBASIC Command Options (By Name) */</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options&diff=344Custom QMBASIC Options2009-04-07T03:21:09Z<p>Glenb: New page: == QMBASIC Command Options (By Name) == '''INPUT''' ''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement. '''INPUT@'...</p>
<hr />
<div>== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
The preceeding options are currently in testing.. This note will be removed when workdevbranch1 has been updated. -GCB</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=QMBASIC_Enhancements&diff=343QMBASIC Enhancements2009-04-07T03:21:00Z<p>Glenb: /* OpenQM GPL Custom Enhacements */</p>
<hr />
<div><br />
== OpenQM GPL Custom Enhacements ==<br />
<br />
[[Custom Compiler Modes]] - A list of custom compiler modes and usages.<br />
<br />
[[Custom QMBASIC Options]] - A list of QMBASIC commands and their custom options, by command name.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=QMBASIC_Enhancements&diff=342QMBASIC Enhancements2009-04-07T03:20:33Z<p>Glenb: /* OpenQM GPL Custom Enhacements */</p>
<hr />
<div><br />
== OpenQM GPL Custom Enhacements ==<br />
<br />
[[Custom Compiler Modes]] - A list of custom compiler modes and usages.<br />
<br />
[[Custom QMBASIC Options]] - A list of QMBASIC commands and their custom options, but function name.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=QMBASIC_Enhancements&diff=341QMBASIC Enhancements2009-04-07T03:19:57Z<p>Glenb: /* OpenQM GPL Custom Enhacements */</p>
<hr />
<div><br />
== OpenQM GPL Custom Enhacements ==<br />
<br />
[[Custom Compiler Modes]] - A list of custom compiler modes and usages.<br />
<br />
[[Custom QMBASIC Options(By Command Name)]] - A list of QMBASIC commands and their custom options, but function name.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=QMBASIC_Enhancements&diff=340QMBASIC Enhancements2009-04-07T03:18:30Z<p>Glenb: /* OpenQM GPL Custom Enhacements */</p>
<hr />
<div><br />
== OpenQM GPL Custom Enhacements ==<br />
<br />
[[Custom Compiler Modes]] - A list of custom compiler modes and usages.<br />
<br />
[[Custom QMBASIC Options(By Function Name)]] - A list of QMBASIC commands and their custom options, but function name.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=QMBASIC_Enhancements&diff=339QMBASIC Enhancements2009-04-07T03:18:03Z<p>Glenb: /* OpenQM GPL Custom Enhacements */</p>
<hr />
<div><br />
== OpenQM GPL Custom Enhacements ==<br />
<br />
[[Custom Compiler Modes]] - A list of custom compiler modes and usages.<br />
<br />
[[Custom QMBASIC Options(By Command Name)]] - A list of QMBASIC commands and their custom options, but function name.</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options(By_Function_Name)&diff=338Custom QMBASIC Options(By Function Name)2009-04-07T03:17:12Z<p>Glenb: /* QMBASIC Function Options (By Name) */</p>
<hr />
<div><br />
== QMBASIC Command Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
The preceeding options are currently in testing.. This note will be removed when workdevbranch1 has been updated. -GCB</div>Glenbhttps://scarlet.deltasoft.com/index.php?title=Custom_QMBASIC_Options(By_Function_Name)&diff=337Custom QMBASIC Options(By Function Name)2009-04-07T03:05:21Z<p>Glenb: /* QMBASIC Function Options (By Name) */</p>
<hr />
<div><br />
== QMBASIC Function Options (By Name) ==<br />
<br />
'''INPUT'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
'''INPUT@'''<br />
''NOCASEINVERT'' - This option ignores the case inversion state of PTERM during the single execution of the statement.<br />
<br />
The preceeding options are currently in testing.. This note will be removed when workdevbranch1 has been updated. -GCB</div>Glenb