Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : TC2000 Users Technical Analysis Forum -- Ignore unavailable to you. Want to Upgrade?

To: deep_rough who wrote (1152)	11/5/1998 6:06:00 PM
From: Sean W. Smith	Respond to of 3291

Now Sean, are you really being completely honest when you say that it's easier to write a scan in QP2 than it is in QP1? And the funny thing is, I could have never figured this out without your help. I can show your ten more that are easier in QP2 than Qp1. Personally I find the for loop structure very straightforward. Here are some reasons i think R2 is easier than R1. 1. More english like syntax. 2. Lines are terminated by ; and not white space which reduces lots of cut and paste errors. 3. syntax looks more like BASIC which is well documented and well know by many people around the world. The R1 syntax bore little resemblence to anything. 4. Better syntax error messages.... 5. Little GUI for creating scan profiles versus providing command line paramters. 6. More included scans than R1. 7. Tons of scans on Brookes Website for QP2. 8. Lots of users willing to help with QP2 scans. I hate #5. But its easier for novices to select a check box than have to type in the filename as with R1. I think my QP2 scan is far more straightforward and easy to understand for the novice than the R1 equivalent. I admit the docs suck but I don't see why you would say its harder. I would call the fact that R1 never printed multiple values a huge limitation as it makes it impossible to write many kinds of scans. It happend to suit your needs so you thinks its feature. I always thought it was a bug because I couldn't tell which date the first of multiple occurances happened on. So what are you using now that you couldn't code your scan in TC2000. Sean