Jens Gustedt wrote: > ELISP> (read "(123 999999999999999999 432)") > *** Eval error *** Invalid read syntax: "Integer constant > overflow in reader", "999999999999999999", 10
So GNU Emacs rolls integers that are too large over, but XEmacs doesn't. ELISP> (read "(123 999999999999999999 432)") (123 123994111 432) > Probably not much usefull by itself. So you might want to try-catch it > (or however this construct might be called in elisp) ? What about checking `most-positive-fixnum'? No actually that probably wouldn't work at all. Perhaps one doesn't need to use `read' at all? Though I guess it's the easiest way to extract information from the buffer (which is what I think is happening), and lots of other things might break if one didn't. (Actually scrap that idea). Oh dear, that was a completely useless post. PS: yes there are people out here. :) -- lawrence mitchell <[EMAIL PROTECTED]> _______________________________________________ Tramp-devel mailing list [EMAIL PROTECTED] http://mail.freesoftware.fsf.org/mailman/listinfo/tramp-devel
