Tweet
Two very specific changes in the current limits of PowerBasic 3.5
for DOS (And upward into LINUX when ..) would greatly help me.
First request:
* Is there any practical way to increase the maximum size of a
* TYPE structure from the current 16384 byte limit to 32768 bytes?
I badly need more struct room in my professional management case
template storage design for the data storage file. I use the TYPE
struct concept to orchestrate the record for the file. Right now
the only way I can see to handle the needed data storage space is
to make a side-saddle second file which uses the same record
pointer number as the primary file, then get the same record number
from the second TYPE structure from the side-saddle file. If the
above could be accomodated, the program suite update for the future
would only then likely be to simply merge the two files back into
what is now only one file. But I'd know where I was headed in the
future when the new product came available.
Second request:
* Is there any way to expand the allowable number of call parameters
* from the current 16 to 64?
Even that isn't quite large enough for my worst case SUBS that have
been very successfully used for years. But 64 would be a HUGE help.
I really don't want to use PUBLIC any more than some folks have for
so long advised one not to do. But without an expansion of a current
allowable maximum number of calling parameters to SUBS there is simply
no help in cleaning this up from code which has been working very
beautifully for many years with a carefully orchestrated PUBLIC venue
of variables.
Thank you very much for what could be done here. I believe that to
do both of the above would significantly improve the PB toolset for
use in very large facility wide program suites like my product.
------------------
Mike Luther
[email protected]
for DOS (And upward into LINUX when ..) would greatly help me.
First request:
* Is there any practical way to increase the maximum size of a
* TYPE structure from the current 16384 byte limit to 32768 bytes?
I badly need more struct room in my professional management case
template storage design for the data storage file. I use the TYPE
struct concept to orchestrate the record for the file. Right now
the only way I can see to handle the needed data storage space is
to make a side-saddle second file which uses the same record
pointer number as the primary file, then get the same record number
from the second TYPE structure from the side-saddle file. If the
above could be accomodated, the program suite update for the future
would only then likely be to simply merge the two files back into
what is now only one file. But I'd know where I was headed in the
future when the new product came available.
Second request:
* Is there any way to expand the allowable number of call parameters
* from the current 16 to 64?
Even that isn't quite large enough for my worst case SUBS that have
been very successfully used for years. But 64 would be a HUGE help.
I really don't want to use PUBLIC any more than some folks have for
so long advised one not to do. But without an expansion of a current
allowable maximum number of calling parameters to SUBS there is simply
no help in cleaning this up from code which has been working very
beautifully for many years with a carefully orchestrated PUBLIC venue
of variables.
Thank you very much for what could be done here. I believe that to
do both of the above would significantly improve the PB toolset for
use in very large facility wide program suites like my product.
------------------
Mike Luther
[email protected]
Comment