64-bit Indicator Values

[m***@gmail.com]

I'd like any thoughts or opinions regarding the feasibility of implementing
64-bit indicator value support. Also would this be a fairly involved
project?

I'd like to pass pointers to it so I'll need 64-bit integer support. My
current thought is to maintain a table mapping 32-bit indicator values to
32 or 64-bit application values. I'd use the indicator values to
communicate with Scintilla and return the mapped value to my application.
It's only brainstorming at this time. If native 64-bit indicator value
support existed that would be ideal, but if it's going to be too time
consuming to do with my novice C++ skills I'll just go with my table idea.
I've worked with C/C++ in an educational setting and to make minor tweaks
to one of the lexers only. Add to that my inexperience with and utter
disdain for Visual Studio 2010 and things move along slowly to say the
least.

Thanks,
Michael

[Neil Hodgson]

I'd like any thoughts or opinions regarding the feasibility of implementing 64-bit indicator value support. Also would this be a fairly involved project?

The extra memory use may be a problem for some applications and implementing an option to choose between the two would be some work. Also, on 32-bit platforms much of Scintilla, including calls, use 32-bit quantities so it would be difficult to report the value to the application.

A fork that only implemented indicator values that are the same width as pointers (sptr_t) would be fairly simple but then you'd have to maintain the fork.

I'd like to pass pointers to it so I'll need 64-bit integer support. My current thought is to maintain a table mapping 32-bit indicator values to 32 or 64-bit application values.

That should work.

Neil

[m***@gmail.com]

Post by Neil Hodgson
A fork that only implemented indicator values that are the same width as

pointers (sptr_t) would be fairly simple but then you’d have to maintain
the fork.

That's exactly what I'm after. I'll play around with it.

Thanks,
Michael

Post by Neil Hodgson

Post by m***@gmail.com
I'd like any thoughts or opinions regarding the feasibility of

implementing 64-bit indicator value support. Also would this be a fairly
involved project?
The extra memory use may be a problem for some applications and
implementing an option to choose between the two would be some work. Also,
on 32-bit platforms much of Scintilla, including calls, use 32-bit
quantities so it would be difficult to report the value to the application.
A fork that only implemented indicator values that are the same width
as pointers (sptr_t) would be fairly simple but then you’d have to maintain
the fork.

Post by m***@gmail.com
I'd like to pass pointers to it so I'll need 64-bit integer support. My

current thought is to maintain a table mapping 32-bit indicator values to
32 or 64-bit application values.
That should work.
Neil