>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
This doesn't make sense in XEmacs since bytes are never exposed
to
Lisp. I'd have to see the use cases to figure out how we would
handle it.
I'll try to explain but I'm afraid it is more or less what I wrote
earlier.
There is a tool, godef, that for example, can print info about an
identifier in a go program. You can select the identifier by giving an
offset for its location in the file given in bytes. Not characters,
bytes. Godef can also read the program on stdin and then the offset
for the interesting identifier is also in bytes.
So gomode would like to feed the current buffer to godef (in utf-8)
and give the position in bytes for the identifier it wants to get some
info about.
[...]
I don't know. I think we should avoid it if at all possible. As
far
as I can see it can't be used for anything that can't be done
otherwise. It's purely a dangerous optimization.
I guess we could try to convince the authors of godef to add an option
to supply the offset in characters instead of bytes (and probably send
them a nice patch that implements it.)
Or we could adjust to the world outside and implement some way for
lisp to know, calculate!?, the underlying byte implementation for each
encoding. (If it makes it easier we would only need to support utf-8
since a go program must be that) So that position-bytes could be
supported.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta