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 : TA-Quotes Plus -- Ignore unavailable to you. Want to Upgrade?

To: TechTrader42 who wrote (2586)	12/1/1997 4:17:00 PM
From: Carolyn S.	Read Replies (2) \| Respond to of 11149

Hi - I am awaiting my Quotes Plus package. I've been using TC2000 up till now. I have a few questions... 1. I saw one message here referring someone to "the help thread". I only see one other thread for Quotes Plus and it's a ghost town. But this thread seems devoted to testing the beta. Is there really a "help thread" for the current release ? 2. Can someone, without violating any non-disclosure agreements, summarize for me the enhancements in version 2 beta versus the release ? I am especially interested in scan language improvements, and also in whether the version 2 can seamlessly integrate deeper CD history data with recent history on HD. 3. Need any more beta-testers ? 4. <Some geek stuff probably of little interest to non-programmers>... I agree that "NO RESET" variables (like the C language "static" variables within a subroutine) would be very useful in the scan language. I also have a question regarding disk access speed as a bottleneck. I am not real familiar with programming Intel platfroms, but I have found I can speed up disk operations a lot on some other systems, when I need to read sequential small amounts of data, by creating my own RAM buffers, reading 4-8K or more into the buffer at a time, and getting my data directly from my buffer with hand-rolled myfgets()/myseek() functions. If the whole data file is small enough to read into some allocated RAM, and especially if random access is needed, I load the whole file and either treat it directly as an array (if its records are fixed size) or go through it just once and build an array of pointers to the records (for variable-size records). This helps speed a LOT if you also need to write to the drive because the head can stay where the writing needs to go. So far, Unix is the only OS I've programmed where this does not get you major speedups. Unix IO must have really good buffering already because even single character file IO is fast in Unix. Carolyn S.