|
PureBytes Links
Trading Reference Links
|
<x-flowed>
This would not verify. Error message said it had a function problem. Also
it threw a rock at my neighbors window. Just kidding about the rock:)
Robert
At 02:08 AM 7/21/00 -0500, M. Simms wrote:
>VH filter: Check this out.....originated in TASC....improved by me. Similar
>to the ADX, but I think it's lighter-weight.
>
>Tracks nicely with the ADX with the added bonus of remaining in basically
>the same range over a long period of time....usually 0.3(weak trend) ->
>1.3(strong trend).
>Actually, it's not a bad turning point detector either.
>
> > -----Original Message-----
> > From: Gary Fritz [mailto:fritz@xxxxxxxx]
> > Sent: Wednesday, July 19, 2000 12:30 PM
> > To: VBatla@xxxxxxx
> > Cc: omega-list@xxxxxxxxxx
> > Subject: Re: EXE code to large?
> >
> >
> > > I'm trying to add the ADX to a system. I'm entering:
> > > value1 = ADX(14);
> > > When I do this and verify I get: "EXE code to large and Variables
> > > and arrays cannot be passed to function lowest" messages.
> > > Any ideas on how to resolve this?
> >
> > Don't use ADX. :-\
> >
> > Seriously, ADX is a huge function. Or, rather, it calls several huge
> > functions (DMIplus, DMIminus, etc) It adds a LOT to your executable
> > size.
> >
> > You were apparently fairly close to the limit before. ADX has pushed
> > you over -- maybe way over. You could try commenting out chunks of
> > code to get an idea for how much you'd have to trim to get around the
> > problem. If it's a system, can you move some of the logic into an
> > IncludeSystem? Functions add to your executable size, but
> > IncludeSystems don't.
> >
> > Gary
> >
>
>
</x-flowed>
|