23.02.2016 21:47, Adriano dos Santos Fernandes wrote:
> Hi!
>
> Debug cpp files generated from epp ones are a nightmare.
>
> The debugger goes/shows cpp line numbers where you want to see epp lines.
>
> Gpre has some support for #line directive but was not working properly.
>
> Attached I put a pat
Hi!
Debug cpp files generated from epp ones are a nightmare.
The debugger goes/shows cpp line numbers where you want to see epp lines.
Gpre has some support for #line directive but was not working properly.
Attached I put a patch to fix it. It's rudimentary, it overloads std C
functions (*put*,
Strange Stored Proc Behaviour with Blob Blob Variables
--
Key: CORE-5114
URL: http://tracker.firebirdsql.org/browse/CORE-5114
Project: Firebird Core
Issue Type: Bug
Components: En
Currently Firebird.pas can be found only in the linux builds.
That's what Alex is talking about. It should be on Windows builds too.
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
NSG> Alex Peshkoff a écrit :
>> Taking into an account that pascal interface appears to
+1
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
AP> Taking into an account that pascal interface appears to be stable enough
AP> and people start to experiment with it I suggest to add build of that
AP> unit to windows build and package it in windows packages. For
Alex Peshkoff a écrit :
> Taking into an account that pascal interface appears to be stable enough
> and people start to experiment with it I suggest to add build of that
> unit to windows build and package it in windows packages. For linux this
> unit is built (using cloop) and placed into bina
Hello,
I'm trying to compile Firebird on OS X El Capitan to understand why it
does not compile in LibreOffice [0]. But I can't compile it directly
either. I had issues with ICU configuration, but at least this issue
can be fixed directly in the code: CTest.c from cloop includes
but this is deprec
Taking into an account that pascal interface appears to be stable enough
and people start to experiment with it I suggest to add build of that
unit to windows build and package it in windows packages. For linux this
unit is built (using cloop) and placed into binary package.
Alex,
---