U++ forum: Welcome to the forum

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

Sat, 15 March 2008 18:53

Shire
Messages: 41
Registered: September 2006
Location: Russia, Yamal peninsula

Member

Quote:

What Esc does is to have only 3 basic value types - number, array of anything and map of anything.
Ignoring effectivity, this covers everything you ever need...

User cannot differ array of numbers and string, and cannot debug wrong conversion. Strings can have stronger restrictions and easy native processing routines (without double conversation to and from WString)

Quote:

I do not quite see how path processing is inferior to e.g. C. In fact, C seems to implement all strings as array of numbers just like Esc...

� - strong typed language. But treating char* as string is the heritage of the low-level past. Now (in C++) this pointer incapsulated in typed std::string or String. Compare String and Vector<char> Wink

Quote:

OK, good point. I guess we should divide to CoreStdLib (without file ops) and StdLib - correct?

Well, I prefer more modular structure. Like Std, StreamIO, FileIO, Codecs, DateTime, SQL, etc. It can help apply restrictions easier.

Quote:

Well, if you have time, you can try to optimize EscValue

Yes, I'll try it.

Report message to a moderator