In our previous episode, leledumbo said: > > IMHO a substituting bad with worse is not a good reason. Java/CIL needs > this > > because its strings are immutable, and character access is expensive. We > > don't share, nor plan to share that trait. > > I hope so, and with Delphi plans on making strings immutable in the future, > I hope FPC doesn't follow.
(doesn't it already for the jvm port?) > Otherwise, simple string concatenation loop will > need to be changed to use string buffers, which makes it more error prone, > more typing and more resource eating. Such things would invalidate half of my codebases, private and work. I don't see the synergy of such new versions with the current products (FPC or Delphi). Same problem I had with e.g. PRISM. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
