CompuServe Messages

Thanks for the reply. I can accept your explanation, but as you say, as a user of the compiler I would be very wary of writing that way. I also see the range/overflow checking as a useful safeguard, to be turned off before the last "release" compile or for evaluating the real speed of the code. For that reason alone, I wouldn't write code that creates range errors, even if performance suffers slightly – it makes it too difficult to separate _real_ bugs (unexpected range errors) from the known ones. Anyway, so far the new Strings module works fine. Thanks for all your efforts. On another subject – I'd like to ask if you could add a couple of features to the editor: 1. I really miss a built-in command for "delete current line". I know you can do it by selecting text and then deleting it, but I find it much easier to have a single key to do it. Currently I assign the macro to that function, but I'd rather save that for other things. 2. Would it be possible to have the editor automatically disable the Correct Case and Wordcomplete functions when typing comments and quoted strings? Probably it's too difficult to make this work for multiple-line comments. I'd be satisfied if the feature only worked when comment and quote characters exist on the current line. Joel