Re: [fpc-devel] Exceptions on wiki

2018-08-01 Thread Sven Barth via fpc-devel
Kirinn schrieb am Mi., 1. Aug. 2018, 23:30: > Hi all, > > Inspired by Gareth aka. Kit's infectious enthusiasm, and the recent long > discussion on exceptions on this list, I wrote up an article on > Exceptions on the FPC wiki. (Strangely enough we didn't have one before.) > > http://wiki.freepasc

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Ryan Joseph
> On Aug 1, 2018, at 3:28 PM, Sven Barth via fpc-devel > wrote: > > If you'd look at the code you quoted you'd see that this is only inserted > *inside* a destructor (the check for potype_destructor; current_procinfo is > the currently compiled routine). So, no, your code is not enough. You

Re: [fpc-devel] Exceptions on wiki

2018-08-01 Thread Paul Breneman
On 07/31/2018 08:32 PM, Kirinn wrote: Hi all, Inspired by Gareth aka. Kit's infectious enthusiasm, and the recent long discussion on exceptions on this list, I wrote up an article on Exceptions on the FPC wiki. (Strangely enough we didn't have one before.) http://wiki.freepascal.org/Exceptio

Re: [fpc-devel] Exceptions on wiki

2018-08-01 Thread J. Gareth Moreton
Infectious enthusiasm - I like that! I'm honoured. It's a good start on the Wiki article.  For more advanced things, you might want to mention how you can use "raise" to re-raise an exception in an except block, and the fact that SysUtils has code that wraps interrupts like SIGSEGV and SIGFPE on

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Ben Grasset
Forgot to mention a record or object with at least one method will get to the first part also, but never the FreeInstance part as they can never have destructors. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bi

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Ben Grasset
> On Wed, Aug 1, 2018 at 11:27 AM, Ryan Joseph wrote: > Yeah, this is the first place I looked but current_structdef is always nil so it never progresses past that point. > Is this test program not enough to get FreeInstance called? You need to declare a class, and give that class at least one me

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Ben Grasset
> I’m still trying to find this with no luck. Doing a quick search for the word "freeinstance" in the compiler source shows two places where it looks for a member function with that name in the global "current_structdef" variable. I'm fairly certain the one you're looking for is in a function call

[fpc-devel] Exceptions on wiki

2018-08-01 Thread Kirinn
Hi all, Inspired by Gareth aka. Kit's infectious enthusiasm, and the recent long discussion on exceptions on this list, I wrote up an article on Exceptions on the FPC wiki. (Strangely enough we didn't have one before.) http://wiki.freepascal.org/Exceptions I hope it'll be useful, and not ent

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Sven Barth via fpc-devel
Ryan Joseph schrieb am Mi., 1. Aug. 2018, 17:28: > > > > On Aug 1, 2018, at 9:17 AM, Sven Barth via fpc-devel < > fpc-devel@lists.freepascal.org> wrote: > > > > Search the compiler's source for the string 'FREEINSTANCE'; you'll find > two locations, one in ngenutil and one in psub. The latter is

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Ryan Joseph
> On Aug 1, 2018, at 9:17 AM, Sven Barth via fpc-devel > wrote: > > Search the compiler's source for the string 'FREEINSTANCE'; you'll find two > locations, one in ngenutil and one in psub. The latter is the one you want. > Yeah, this is the first place I looked but current_structdef is al

Re: [fpc-devel] FreeInstance

2018-08-01 Thread Sven Barth via fpc-devel
Ryan Joseph schrieb am Di., 31. Juli 2018, 22:29: > > > > On Jul 31, 2018, at 9:56 AM, Ryan Joseph > wrote: > > > > then how does it get invoked then? there must be some node added > somewhere but I can’t find it. > > I’m still trying to find this with no luck. I suspect there’s a call node > ad

Re: [fpc-devel] Free Pascal 3.0.6

2018-08-01 Thread Marco van de Voort
In our previous episode, African Wild Dog said: > Are there plans to release version 3.0.6 later this year? No. There will probably no 3.0.x anymore. (and even if, it would have mostly minor RTL fixes, no sensitive compiler fixes). The next release will be from trunk as 3.2, but considering histo