Re: [fpc-devel] Internal symbols

2019-02-03 Thread Mattias Gaertner via fpc-devel
On Sun, 03 Feb 2019 04:08:46 + "J. Gareth Moreton" wrote: >[...] > Lazarus doesn't even display the error (see bug #34996) Fixed. Mattias ___ fpc-devel maillist - fpc-devel@lists.freepascal.org

Re: [fpc-devel] Internal symbols

2019-02-03 Thread Jonas Maebe
On 03/02/19 17:12, J. Gareth Moreton wrote: Fair enough.  What about calling functions like Int via assembly language, since it's currently impossible to do it either via the internal function or using the public symbol that maps to it, since "CALL int" just raises a linker error - I presume

Re: [fpc-devel] Internal symbols

2019-02-03 Thread J. Gareth Moreton
Fair enough.  What about calling functions like Int via assembly language, since it's currently impossible to do it either via the internal function or using the public symbol that maps to it, since "CALL int" just raises a linker error - I presume it's not as easy as copying some code from

Re: [fpc-devel] Internal symbols

2019-02-03 Thread Jonas Maebe
On 03/02/19 05:08, J. Gareth Moreton wrote: Basically, if you declare a public symbol (either using the "public" directive or putting it in the interface section of a unit) with a name that's identical to an internal symbol (I used "FPC_ABSMASK_DOUBLE"), you get a 'duplicate symbol' linker

[fpc-devel] Internal symbols

2019-02-02 Thread J. Gareth Moreton
Hi everyone, So I've come across a couple of issues recently regarding internally-defined symbols.  One of them involves assembly language, which is always asking for trouble, but one can be triggered through regular Pascal code. Basically, if you declare a public symbol (either using the