Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Ben Grasset
On Fri, Feb 15, 2019 at 3:33 PM Jonas Maebe wrote: > As mentioned by others, that's not really something any of the current > FPC developers are interested in working on. Martin Schreiber, however, > was working on a project like that before he passed away > I don't want to speak ill of the dead

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Ben Grasset
On Fri, Feb 15, 2019 at 4:07 AM James via fpc-devel < fpc-devel@lists.freepascal.org> wrote: > I'm interested in starting (or joining) a discussion on the next (*non* > backwards compatible) version of FPC. Instead of being classically object > oriented, there is merit in examining a model with ad

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Neil Graham
On 17/02/19 10:37 AM, Ralf Quint wrote: On 2/14/2019 9:28 PM, James via fpc-devel wrote: I'm interested in starting (or joining) a discussion on the next (*non* backwards compatible) version of FPC. Instead of being classically object oriented, there is merit in examining a model with ad-hoc p

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Sven Barth via fpc-devel
Am Sa., 16. Feb. 2019, 23:44 hat Benito van der Zander geschrieben: > > > but we try as much as possible to break old code. > > > I have noticed that. All my code has been broken by the codepage aware > strings and TEncoding > Introduction of the codepage aware AnsiString was one of the disrupti

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Ralf Quint
On 2/16/2019 12:43 AM, Florian Klämpfl wrote: but we try as much as possible to break old code. Really? =-O Ralf ;-) --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ fpc-devel maillist -

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Benito van der Zander
Hi, there is NewPascal with improved memory safety/smart pointers: http://newpascal.org/ but we try as much as possible to break old code. I have noticed that. All my code has been broken by the codepage aware strings and TEncoding and FPC's goal to remain Delphi-compatible. So are

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Mattias Gaertner via fpc-devel
On Sat, 16 Feb 2019 13:37:44 -0800 Ralf Quint wrote: >[...] > Adding newfangled gadgets and gizmos might be all fine and dandy, but > don't force it down the throat of everyone as a must. I am not going > to throw away 40 years of libraries and snippets away and start from > scratch, just so so

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Ralf Quint
On 2/14/2019 9:28 PM, James via fpc-devel wrote: I'm interested in starting (or joining) a discussion on the next (*non* backwards compatible) version of FPC. Instead of being classically object oriented, there is merit in examining a model with ad-hoc polymorphism like Rust. I am, like appar

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Sven Barth via fpc-devel
Am Sa., 16. Feb. 2019, 09:58 hat Michael Van Canneyt geschrieben: > > > On Sat, 16 Feb 2019, J. Gareth Moreton wrote: > > > Hm, fair enough. Seems a bit strange to not like a new feature, although > > Delphi did start getting a bit bloated in places. Ah well! > > Compatibility is never a bad th

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Michael Van Canneyt
On Sat, 16 Feb 2019, J. Gareth Moreton wrote: Hm, fair enough.  Seems a bit strange to not like a new feature, although Delphi did start getting a bit bloated in places.  Ah well!  Compatibility is never a bad thing though! Hm. 'a bit bloated' is the understatement of the year. I still prog

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Florian Klämpfl
Am 16.02.19 um 09:50 schrieb Mattias Gaertner via fpc-devel: On Sat, 16 Feb 2019 09:43:32 +0100 Florian Klämpfl wrote: [...]but we try as much as possible to break old code. Then you are not doing a good job. ;) Oh :) ___ fpc-devel maillis

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Mattias Gaertner via fpc-devel
On Sat, 16 Feb 2019 09:43:32 +0100 Florian Klämpfl wrote: >[...]but we try as much as possible to break old code. Then you are not doing a good job. ;) Mattias ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Florian Klämpfl
Am 16.02.19 um 08:29 schrieb J. Gareth Moreton: Hm, fair enough.  Seems a bit strange to not like a new feature, although Delphi did start getting a bit bloated in places.  Ah well! Compatibility is never a bad thing though! "Do not break people's code" is one of FPC design goals. So anything

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread J. Gareth Moreton
Hm, fair enough.  Seems a bit strange to not like a new feature, although Delphi did start getting a bit bloated in places.  Ah well!  Compatibility is never a bad thing though! Gareth aka. Kit On Sat 16/02/19 08:27 , Jonas Maebe jo...@freepascal.org sent: On 16/02/19 01:37, J. Gareth Moreton

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Jonas Maebe
On 16/02/19 01:37, J. Gareth Moreton wrote: One thing that does spring to mind though.,, what features of Delphi and FPC made the language unsuitable for Martin Schreiber, and is it anything we developers can possibly address in some way? He did not like new language features and RTL changes a

Re: [fpc-devel] "Blank slate" next version of FPC

2019-02-16 Thread Marco van de Voort
Op 2/16/2019 om 1:37 AM schreef J. Gareth Moreton: That's an interesting project there. One thing that does spring to mind though.,, what features of Delphi and FPC made the language unsuitable for Martin Schreiber, and is it anything we developers can possibly address in some way? Martin w