| PLEX86 | ||
Where should the type information be 170Where should the type information be 171 Yes, I understand that. TOPS-10 had oodles of customers who did exactly the same thing. The trick is to figure out what can be implemented that is not Rubin-specific but general-user... your part of To be clear on my part, my problem is that he typically is NOT telling us what he needs as a user. Too often he tells us how to implement what he thinks he needs. Because he is often not clear in his statements about what his ultimate goals are, and he is unwilling or unable to to either understand the details or the terminology of language design and implementation, it is clear that his description of the implementation is incorrect. It is not clear what sort of implementation would meet his needs, or even if such an implementation is possible. It is also not clear that his needs match those of a significant body of other users. and Unfortunately, while the implementation of new math concepts is one of his interests, so is high performance, which he often appears to want to achieve by getting direct access to common machine operations, and compiler optimization of his expressions. For example, you interpreted his statements as implying simply that he wanted to type fewer characters, I suspected, and I believe his subsequent posts have confirmed this, that he thought making something an operator would somehow help his programs attain higher performance.
|
||||
Where should the type information be 171 Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet
|
||||