Hi,

Attached is a patch for utrace.pp and grids.pp/

It removes the redundant TAssertProc definition and uses define VER1_1 instead of NEW1_1 to compiler. The lcl can be compiled with fpc 1.1.

I want to use fpc 1.1 for lazarus, so we can use interfaces and use the win32 browse for folder dialog.

I cannot compile synedit with fpc 1.1. It gives a duplicate label error. Is there a list of fpc bugs which prevent fpc 1.1 to compile lazarus?

Vincent.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gz00033.gz
Type: application/octet-stream
Size: 611 bytes
Desc: "fpc1.1.patch.gz"
Url : http://localhost/pipermail/lazarus/attachments/20030814/2b26f893/gz00033.obj

--- Vincent Snijders escribi�: > Hi,

You can workaround the problem wrapping the boolean expression that fails between "(", ")". The problem its known to the fpc team and they made a test program for it. I wish you luck compiling lazarus with the current 1.1 compiler!.

Jesus Reyes A.

_________________________________________________________ Do You Yahoo!?
La mejor conexi�n a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx

It looks very promising. I will try and use it.

Thanks,
Vincent.

The NEW1_1 indicates the difference between the last working fpc 1.1 (the rpm on the website) and the current (NEW1_1). We can change the NEW1_1 to VER1_1, when we
a) remove the fpc 1.1 rpm
b) create a new fpc 1.1 rpm

I want to use fpc 1.1 for lazarus, so we can use interfaces and use the win32 browse for folder dialog.

We don't need interfaces for the win32 browse dialog. It would only make things nicer.

I cannot compile synedit with fpc 1.1. It gives a duplicate label error. Is there a list of fpc bugs which prevent fpc 1.1 to compile lazarus?

Last time I check it was only this one. The rest was fixed by workarounds.

Mattias

"Vincent Snijders" wrote

I want to use fpc 1.1 for lazarus, so we can use interfaces and use the win32 browse for folder dialog.

There's no need for 1.1. There are functions CoTaskMemAlloc and CoTaskMemFree in WinAPI. According to MSDN first of them "Allocates a block of task memory in the same way that IMalloc::Alloc does". I wrote a unit with implementation of SelectDirectoryProc (using SHBrowseForFolder function):
http://virrar.republika.pl/win32dirsel.pas
and simple test program:
http://virrar.republika.pl/test.pas
and all seems to work OK.
I wanted to implement TSelectDirectoryDialog in Win32 interface but I can't do it now (I'm going on a trip right now). Maybe you will do this using this unit?

I would keep this under ifdefs, though, because 1.1 is not always stable, and interfaces have not been tested extensively.

Michael.