Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

[fredvs]

> The Delphi XE, a "code aware string type" 

Ha, ok, thanks for the clear explanation.

I did not test yet deeply strings feature of mselang.
At first look, there are type string8, string16, string32 but did not test
the features.

Other thing.
About some reactions in fpc-dev mailing list about MSElang:

http://lists.freepascal.org/pipermail/fpc-devel/2019-February/040196.html

Strangely my post does not appear.
Maybe it is better because I was too hot after reading some total lies.

But there are interesting post too, like this: 

> On Sat, 16 Feb 2019, J. Michael Van Canneyt wrote:
> I still program mostly using language features of essentially D7. 
> Works fine, and I don't think my productivity is in any way enhanced by
> all the new features.

I still have (big) Windows GUI projects in production, mainly
query-databases, that use Pascal code via Delphi 7.
Those projects are regularly updated and compiled with that old Delphi 7.
All still work like charm.

I did try some miraculous new Delphi features like generic for example.
Yes it is cool but in the real world, as I sensed, it appends conflict
sometimes.
So I do not use generic any more (and at the end, no much lines of code
spared). 

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

[Michael Schnell]

> 
> but what is "code aware strings" ?

The Delphi XE, a "code aware string type" can be defined to hold different 
types of Data by adding a number in parentheses  to the "string word in the 
definition. E.g. "TMyString = String(CP_ACP)"; there is a definition CP_ACP = 
0; meaning default ANSI code page, or "TMyString = String(CP_UTF16) with 
CP_UTF16 being defined = 1200; meaning  utf-16. Hence a String (type) can be 
defined to hole either of several different encoding variants, with an element 
size of either of 1, 2 or 4 bytes. If assigning a string content to some string 
variable, an automatic cote conversion will be done. Martin did think this is 
abysmal. And he is right, as this breaks compatibility in many cases and asks 
for a lot of nasty misconceptions.

Some messages above I wrote: 
I had been discussing this with Martin some two years ago. We agreed that the 
way it's implemented in Delphi (and even more inconsistent) in fpc is not at 
all optimal, and he said he would not do new strings in mselang. I did not hear 
any news about this since that time. In fact I wrote an article about a (IMHO) 
more consistent way to implement code aware strings -> 
http://wiki.freepascal.org/not_Delphi_compatible_enhancement_for_Unicode_Support

-Michael







___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

[fredvs]

> This  shows that it can do Unicode, bit not that it does code aware
strings. 

Hello Michael.

Sorry for my immense ignorance but what is "code aware strings" ?

Goggling "code aware strings" or "code aware strings + delphi" does not give
anything.

;-(

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

[Michael Schnell]

> 
> Please, take a look at this picture:
> 
> 
>

This  shows that it can do Unicode, bit not that it does code aware strings. 


-Michael



___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk