× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Named indicators (was DOW vs DOU)
  • From: "Joe Teff" <jteff19@xxxxxxx>
  • Date: Thu, 29 May 1997 21:49:22 -0500

I've started using a pointer to the indicators (*IN) and then mapping a data 
structure over the indicators. By doing this, I can rename my indicators. For 
example, I rename *IN71 to SFLClear, *IN72 to SFLDisplay and *IN73 to 
SFLControl. Then I use a statement like Eval SFLClear = *On. I think the code 
is so much easier to read and understand using this technique.

Joe Teff
QDS
Bloomington, MN
----------
> I use a block of indicators to track all subfile settings. I haven't done 
> it, but I have toyed with the idea of creating block names for the 
> indicators to be set like CLRSFL and DLTSFL and just doing a MOVEA CLRSFL 
> before writing the ctl record. That way, I know I didn't forget to turn 
> off display ctl or something like that.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.