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.

Technology Stocks : BORL: Time to BUY! -- Ignore unavailable to you. Want to Upgrade?

To: Steve Booth who wrote (6871)	10/24/1997 7:43:00 PM
From: Kashish King	Respond to of 10836

The pointer remark was TIC since the target participant made that comment once. Obviously a reference-based design (pointers period for user-defined types) is far superior in the vast majority of cases and intrinsic types still have their by-value behavior as one intuitively expects of numbers. AFA the double equal, the compiler can warn about that but I wasn't aware it was that big of a problem for the average C++ programmer.

To: Steve Booth who wrote (6871)	10/24/1997 11:29:00 PM
From: i-node	Read Replies (1) \| Respond to of 10836

Pointers and a single equal sign on if comparisons cause the vast majority of problems in "C". You can certainly write an OS without pointers; however, the question of efficiency becomes very big. Efficiency both in execution and in development. In my mind, pointers provide a level of flexibility that is essential for a lot of projects. Errant pointers are not a problem if you use appropriate debugging techniques. Most compilers will warn about a single equal sign comparison if it is atypical for the context. While I believe Java/JBuilder will be a success, there are many applictions for which it will never be suitable -- at least not in anything approaching its current form.