On 2 January 2014 00:06, Marco van de Voort <[email protected]> wrote: > On Wed, Jan 01, 2014 at 08:03:07PM +0000, Graeme Geldenhuys wrote: > > > Still it might not be a bad idea to make such things a string instead > of a > > > character in time. > > > > Hence in fpGUI I have a TfpgChar defined as a 4-byte string, and can > > easily be extended if needed. > > Why that? Why not simply a variable length string? > > -- > _______________________________________________ > Lazarus mailing list > [email protected] > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus >
What is needed here is a chart explaining what the options are and the use cases where they apply. This is an area most developers don't understand their code breaks in some way. Without use cases simply quoting standards and how this or that library or API does this or that won't be of any help. A chart explaining where they have gone wrong and what options should apply will be more useful than repeated arguments about what is wrong or what right or wrong paths FPC, Lazarus, Delphi or Microsoft have taken. The experts in this area will have to switch to educator mode rather from developer mode if these arguments are going to end. -- Frank Church ======================= http://devblog.brahmancreations.com
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
