On Wed, 16 Aug 2017 12:24:55 +0200 Michael Schnell via Lazarus <lazarus@lists.lazarus-ide.org> wrote:
> On 16.08.2017 11:51, Mattias Gaertner via Lazarus wrote: > > Every Delphi/FPC type has a bunch of operators. Strings support :=, =, > > <>, >=, <= and [] for read and write. > > When you propose a new string type "dynamicstring" you have to define these > > operators. >[...] > For "new" encoding brandings, such as CP_Byte, CP_Word, CP_DWord, > CP_QWord, the working of the operators is obvious. There are no such codepages. You are confusing people if you name your encodings like this. > It somebody tries to > compare a printable Text string with a string of binary elements, maybe > the behavior is undefined. Your "dynamicstring" supports char, widechar, byte, word, dword, qword. Why not shortint or smallint? Why not boolean, single and variant? What is the intention of your proposal? Mattias -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
