Zvone wrote: >> TBytes was the datatype to be used. However that would break >> backwards compatibility since historically "string" was used >> everywhere. That all was no problem, however the rule is: "DO NOT >> BREAK BACKWARDS COMPATIBILITY" and that is where the problems begin. > > Well you've already broken this rule by using UnicodeString as return > type
The ICS components use "string" since the beginning, it just happend in RDS 2009 that its mapping changed from "AnsiString" to "UnicodeString". Only C++Builder packages always used the mapped type explicitly. > so I don't see a big deal here. Also ICS 7 is used by users that > need to recompile their code in D2009/2010 so they do have to adapt > their code anyway as it won't work properly with D2009 not just with > ICS. No, in Delphi there are no interface changes. Properties, signatures of methods and event handlers did not change. That is different in C++Builder where everything changed from AnsiString to UnicodeString. > For compatibility purposes you have ICS 6 and 5. > > And it's not a big problem - I have 2 ideas then to satisfy everybody > and improve codepages compatibility: > > Idea 1: Why not introduce TPop3Cli.LastResponseTb which would be > identical to LastResponse except different type (TBytes)? Yes, probably we should introduce a new property LastRawResponse: TBytes as workaround. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
