[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Any ideas to stay under 64k barrier ??



PureBytes Links

Trading Reference Links

You can get around this problem using HASHNUMS DLL to
join together a number of systems each smaller than 64K.

There is also a new DLL called QLSNUMS that also helps
with this problme. It allows you to use lists, queues and 
stacks. This DLL has just been updated with Statistical 
functions for lIsts

You can get a free demo of these DLLs with full manual
from the WEB Site:
www.ozemail.com.au/~qtrade.

-----Original Message-----
From:	Jwtrader [SMTP:Jwtrader@xxxxxxx]
Sent:	Wednesday, 11 March 1998 13:40
To:	omega-list@xxxxxxxxxx
Subject:	Any ideas to stay under 64k barrier ??

Hello there fellow Omeganitos and Omeganitas !! ( in harmony with El Nino )

I just joined the Omega list and after reading part way down the Digest
Archaive, I almost turn around and unsubscribe on the same day after seeing
the personal attacks and name calling.  Good thing I didn't, because after
that it got better and better.  It's very refreshing to see the unselfishness
of some members giving their valuable time to help others.  I could only hope
I can do half as good.  Anyway, I am going to try my luck for some help here
today.
     My problem is that I am keep hitting the 64k barrier in my Power Editor
Programming.  It's either " Out of  memory " or "Execute Code too large "
I have tried the following 3 things, but none of them are particularly
satisfactory.

      1) IncludeSystem -too much redundancy, highly inefficent, and awkward to
                                 program.
      2) Part out portion of code to User Functions - appear to be considered
as part
          of 64k block.
      3) Use Global Variables ( from Investment Engineering Corp )- Great
except if
          applying system to many charts could cause a mess trying to keep
track of  
          where all the global values are kept.

My system calculate a series of  Pivot points.  The rest of the program
analyze these points for different patterns.  I don't know anything about C
language and not smart enough in QuickBasic to write DLL's.
      Any ideas on conserving memory in my codes ???
     1) use less variables? length of var names,use ready made var like
value0-99 ?
         recycle var usage?
     2) less comments
     3) Does nestled loop use more memory than 2 separate loop ?
     4) Does a statement of many AND or OR use more memory than several
         separate ones.
     5) Set MaxBarsBack to a min ?
     6) Arrays, strings, etc. ?

Thank you in advance for any help.  I won't be disappointed if I don't get any
response as I believe this might be beyond some member's expertize.

   Happy trading to all !!! and don't be greedy-----
"10% every 10 days on $10,000 compounded will get you a $1 million dollar in
 15 months "  What's your hurry ?
    That's like buying a 1000 shrs of a $20 stk on margin and get a point out
of it every 10 days.

Jim C. Wong