Re: [fpc-devel] Minor request with case else branches

I personally disagree with that one because it's just fluff, considering that "nothing" is equivalent to "{ nothing }" - usually a keyword or an intrinsic should actually do something. Gareth aka. Kit On 27/05/2019 02:33, Ben Grasset wrote: On Fri, May 24, 2019 at 5:46 PM J. Gareth Moreton

Re: [fpc-devel] [PATCH] Add support for Hygon Dhyana processor

On 2019/5/25 2:52, wkitt...@windstream.net wrote: On 5/23/19 5:10 AM, Jinke Fan wrote:   { return base type of processor: 0 - is Unknown, 10 - is AMD (AuthenticAMD), } +    {    10 - is Hygon (HygonGenuine) } is there a problem here? AMD and Hygon are both

Re: [fpc-devel] Closures/anonymous functions update

> On May 26, 2019, at 9:15 PM, Ben Grasset wrote: > > Even if it doesn't happen right away, I 100% agree that this needs to be how > they work eventually (which will not break Delphi compatibility, because how > they work internally is irrelevant as long as the external means to access / >

Re: [fpc-devel] Minor request with case else branches

On Fri, May 24, 2019 at 5:46 PM J. Gareth Moreton wrote: > Whenever I come across a section of code in my own projects where "*else * > ;" is necessary, or any empty branch for that matter, I put a "{ Do > nothing }" comment just to make it absolutely clear that the block is > there deliberately

Re: [fpc-devel] Closures/anonymous functions update

On Sat, May 18, 2019 at 2:57 PM Ryan Joseph wrote: > I wanted to make an alternate capture mode as an optimization for closures > that don’t get passed outside of their scope but I wasn’t able to figure > this out yet (using old-style objects instead of classes). It’s a waste to > allocate a new

Re: [fpc-devel] Compiler picks wrong overload

On Wed, May 22, 2019 at 12:53 PM Pascal Riekenberg wrote: > No one? This is a showstopper! > FWIW, you can comment out the new TBytes definitions as a temporary fix. They are not actually used anywhere in the FPC codebase. More broadly I think the bigger problem is FPC's internal

Re: [fpc-devel] [Core] Minor request with case else branches

Sorry, I didn't mean to post my reply to the core list. I do like things to be documented so there's no guesswork with that.  Admittedly some of the standards seem to be more designed for projects written in C and C++, like identifiers all being in lowercase, whereas Pascal, or at least

Re: [fpc-devel] Object upgrades

> On May 26, 2019, at 5:50 PM, Kostas Michalopoulos > wrote: > > Do records support inheritance in next FPC? 3.0.4 doesn't seem to > allow that and this is the main reason i use objects when i need value > types. No, only objects. Objects don’t have operator overloads though so they can’t be

Re: [fpc-devel] Object upgrades

Do records support inheritance in next FPC? 3.0.4 doesn't seem to allow that and this is the main reason i use objects when i need value types. Actually, what are the differences between records and objects that make it impossible for records to get objects' features or objects to get records'

Re: [fpc-devel] Object upgrades

> On May 26, 2019, at 2:58 PM, Sven Barth via fpc-devel > wrote: > > Keeping them alive is not the same as developing new syntaxes for them (and > for objects that *would* be a new syntax). Also we fix bugs for them which > Delphi does not do. > Can we at least do operators overloads for

Re: [fpc-devel] Object upgrades

Ryan Joseph schrieb am So., 26. Mai 2019, 17:05: > > > > On May 24, 2019, at 4:49 AM, Sven Barth via fpc-devel < > fpc-devel@lists.freepascal.org> wrote: > > > > Please don't. They're legacy types (even though we don't consider them > obsolete) and geared towards the TP behavior and

Re: [fpc-devel] Object upgrades

> On May 24, 2019, at 4:49 AM, Sven Barth via fpc-devel > wrote: > > Please don't. They're legacy types (even though we don't consider them > obsolete) and geared towards the TP behavior and compatibility. > { resending this again because the old message got blocked } I thought FPC was

Re: [fpc-devel] Class management operators

> On May 26, 2019, at 4:02 AM, Sven Barth via fpc-devel > wrote: > > Thus, if we would decide to implement ARC for classes we would integrate > directly inside the compiler, cause there would be no need for user > management (Create and Destroy have the role of the Initialize and Finalize

Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

Just one note of caution: When you encounter strange behaviour of your Code on Cortex-M0 in respect to DIV commmand then check the mailinglist, Jeppe has provided a fix but I am not quite sure if the fix has made it into official trunk. Michael Am 26.05.19 um 09:15 schrieb Dimitrios Chr.

Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

On 2019/05/26 10:25, Dimitrios Chr. Ioannidis via fpc-devel wrote: Hi Christo, PS: I don't see any commits reg. AVR's. Do you have any insight if some of the AVR bug reports ( stack error checking,  DIV, etc ) will be fixed / resolved ? regards. -- Dimitrios Chr. Ioannidis Hi

Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

Hi, Στις 26/5/2019 11:25 π.μ., ο Dimitrios Chr. Ioannidis via fpc-devel έγραψε: < snip> In this bug report there is a link for a patched toolchain . I'll try it later today to see how it goes. Just FYI, the patched

Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

Hi Christo, Στις 26/5/2019 11:10 π.μ., ο Christo Crause έγραψε: On Sun, May 26, 2019 at 9:16 AM Dimitrios Chr. Ioannidis via fpc-devel > wrote: "G:\Programming\dimitris\tools\gcc-arm-none-eabi\bin\arm-none-eabi-objcopy.exe:

Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

On Sun, May 26, 2019 at 9:16 AM Dimitrios Chr. Ioannidis via fpc-devel < fpc-devel@lists.freepascal.org> wrote: > "G:\Programming\dimitris\tools\gcc-arm-none-eabi\bin\arm-none-eabi-objcopy.exe: > G:\Programming\dimitris\tools\mbf\Samples\Blinky\Blinky.hex 64-bit address > 0x4b4fa3 out of

Re: [fpc-devel] Class management operators

Ryan Joseph schrieb am Sa., 25. Mai 2019, 19:55: > > > > On May 24, 2019, at 2:46 PM, Sven Barth via fpc-devel < > fpc-devel@lists.freepascal.org> wrote: > > > > Object Pascal isn't a full ARC language however. Also it is not > something that one can enable on a whim cause it also affects other

[fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

Hi,   yesterday I tried ( for first time ) to use the fpc for arm with the gcc-arm-none-eabi-8-2018-q4-major-win32 toolchain and I got this error : "G:\Programming\dimitris\tools\gcc-arm-none-eabi\bin\arm-none-eabi-objcopy.exe: G:\Programming\dimitris\tools\mbf\Samples\Blinky\Blinky.hex