U++ forum: Welcome to the forum

Re: ESC_STRING and other questions [message #14798 is a reply to message #14797]

Sat, 15 March 2008 11:13

mirek
Messages: 13975
Registered: November 2005

Ultimate Member

Shire wrote on Sat, 15 March 2008 05:37

Is reasonable to add ESC_STRING (internally WString) type? Now strings are represented as arrays of ESC_NUMBER values, with large overhead and collisions when typecasting to StdValue.
Separate string type can faster execution. Strings can declare all array operations and explicit convertions to/from arrays.

That is true. However, this would break "typeless" design paradigm.

Anyway, the idea was to optimize EscValue so that it will store string data as (surprise) WString as long as possible. In fact, maybe even as String - that would only be better Smile

However, so far, despite being ineffective, Esc implementation was "good enough" for target applications...

Quote:

Also, I think, that ESC_MAP's keys can be strictly ESC_STRING or ESC_NUMBER - other types have questionable usability. Key type is possible to detect at definition time.

Ditto

It should be possible to optimize EscValue for this.

Quote:

I also think, that file operations in Standarrd library are unsafe. Would you separate them?

Unsafe? Why?

Quote:

And the last question, will U++ team continue development of Esc?Esc language is very good to understandinh and embedding in application. Additionally, it fully open and compatible with UPP.

Esc is an important part of several comercial applications, so you should not be afraid this is a dead end. We have to maintain it...

The only problem seems to be that generally, current implementation satisfies our need Smile

Means there is only a little reason to optimize Esc.

Mirek

Report message to a moderator