SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Strategies & Market Trends : TA-Quotes Plus

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: gonzongo who wrote (2005)9/21/1997 9:52:00 AM
From: Jeff Grover   of 11149
 
Andy,

Correct (WRT "...multiple if-then-endif scenario only allows one input file and will generate duplicate outputs when the criteria interesect.).

I handle this via post scan processing with Sean's perl script for now (multiple scans produce multiple lists, then I merge to see how many of them a single issue occurs in ... sorta like a DSN_3 or DNS_7 determination). Future plan is to use that database approach (access or excel) I eluded to earlier.

Clearly the best solution would be for Q+R2 to have all of these capabilities, however I view Q+ as a data provider and refrain from depending too much on its list processing capabilities. I've chosen not to belabor the parser and scan syntax at this time as it will likely have the undesirable effect of delaying release of Q+R2. I have been collecting thoughts on this subject with Q+R3 as my implementation target.

....I also wish we could define more then one output file allowing the generation of multiple lists from a single scan.

BTW: another advantage for nested ifs (or switch statements ala C++ or case statements ala Ada) is the increase throughput it affords... the scan (program) whould not spend time checking if something is red, blue, or green if it has already determined it to be yellow.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext