Re: [fpc-pascal] Built in Query language (or abuse)
> A creative idea: Not really, Microsoft is advocating this kind of stuff on .NET basis as LINQ for a few years now. Albeit a bit more functional oriented. Also, read: http://www.freepascal.org/faq.var#extensionselect such loose cannon ideas are pretty useless without a real survey of its implementation and all problems. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
> 2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
>>
>> more info (everything compiled with -dFPC_ARMEL -O- -gl):
>>
>> [EMAIL PROTECTED]:~/source/armtest$ qemu-arm armtest
>> Error: Bad syscall: 90004c
>> qemu: unhandled CPU exception 0x2 - aborting
>> R00=ffda R01=4007f750 R02=4007f758 R03=
>> R04=00018ed0 R05= R06= R07=0090004c
ah, it shouldn't add the base number. this might fix it:
Index: sysnr.inc
===
--- sysnr.inc (revision 11178)
+++ sysnr.inc (working copy)
@@ -21,7 +21,11 @@
}
Const
+{$ifdef FPC_ABI_EABI}
+ syscall_nr_base = $0;
+{$else FPC_ABI_EABI}
syscall_nr_base = $90;
+{$endif FPC_ABI_EABI}
but i'll confirm in a while.
henry
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
2008/6/2 Luca Olivetti <[EMAIL PROTECTED]>: > En/na Luca Olivetti ha escrit: > >> I guess I'll stick to i386 for a while ;-) > > I really think I should. I created a full cross compiler just like Florian > :-D > I compiled a simple hello world and it doesn't run (like the compiler): > > sbox-CHINOOK_ARMEL: ~] > fpc-svn/hello > Error: unimplemented syscall 90004c > qemu: uncaught target signal 6 (Aborted) - exiting > > > tablet: > ~ $ ./hello > Illegal instruction > more info (everything compiled with -dFPC_ARMEL -O- -gl): [EMAIL PROTECTED]:~/source/armtest$ qemu-arm armtest Error: Bad syscall: 90004c qemu: unhandled CPU exception 0x2 - aborting R00=ffda R01=4007f750 R02=4007f758 R03= R04=00018ed0 R05= R06= R07=0090004c R08= R09= R10=00023000 R11=4007f73c R12=4007f740 R13=4007f6fc R14=c798 R15=c200 PSR=6010 -ZC- A usr32 s00=( 0) s01=( 0) d00=( 0) s02=( 0) s03=( 0) d01=( 0) s04=( 0) s05=( 0) d02=( 0) s06=( 0) s07=( 0) d03=( 0) s08=( 0) s09=( 0) d04=( 0) s10=( 0) s11=( 0) d05=( 0) s12=( 0) s13=( 0) d06=( 0) s14=( 0) s15=( 0) d07=( 0) s16=( 0) s17=( 0) d08=( 0) s18=( 0) s19=( 0) d09=( 0) s20=( 0) s21=( 0) d10=( 0) s22=( 0) s23=( 0) d11=( 0) s24=( 0) s25=( 0) d12=( 0) s26=( 0) s27=( 0) d13=( 0) s28=( 0) s29=( 0) d14=( 0) s30=( 0) s31=( 0) d15=( 0) FPSCR: qemu: uncaught target signal 6 (Aborted) - exiting henry ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
> 2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
>> 2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
>>>
>>> more info (everything compiled with -dFPC_ARMEL -O- -gl):
>>>
>>> [EMAIL PROTECTED]:~/source/armtest$ qemu-arm armtest
>>> Error: Bad syscall: 90004c
>>> qemu: unhandled CPU exception 0x2 - aborting
>>> R00=ffda R01=4007f750 R02=4007f758 R03=
>>> R04=00018ed0 R05= R06= R07=0090004c
>
> ah, it shouldn't add the base number. this might fix it:
>
> Index: sysnr.inc
> ===
> --- sysnr.inc (revision 11178)
> +++ sysnr.inc (working copy)
> @@ -21,7 +21,11 @@
> }
>
> Const
> +{$ifdef FPC_ABI_EABI}
> + syscall_nr_base = $0;
> +{$else FPC_ABI_EABI}
> syscall_nr_base = $90;
> +{$endif FPC_ABI_EABI}
>
> but i'll confirm in a while.
>
yes, this works for me. luca, can you try?
> henry
>
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>: > > more info (everything compiled with -dFPC_ARMEL -O- -gl): > > [EMAIL PROTECTED]:~/source/armtest$ qemu-arm armtest > Error: Bad syscall: 90004c > qemu: unhandled CPU exception 0x2 - aborting > R00=ffda R01=4007f750 R02=4007f758 R03= > R04=00018ed0 R05= R06= R07=0090004c > R08= R09= R10=00023000 R11=4007f73c > R12=4007f740 R13=4007f6fc R14=c798 R15=c200 > PSR=6010 -ZC- A usr32 > s00=( 0) s01=( 0) d00=( 0) > s02=( 0) s03=( 0) d01=( 0) > s04=( 0) s05=( 0) d02=( 0) > s06=( 0) s07=( 0) d03=( 0) > s08=( 0) s09=( 0) d04=( 0) > s10=( 0) s11=( 0) d05=( 0) > s12=( 0) s13=( 0) d06=( 0) > s14=( 0) s15=( 0) d07=( 0) > s16=( 0) s17=( 0) d08=( 0) > s18=( 0) s19=( 0) d09=( 0) > s20=( 0) s21=( 0) d10=( 0) > s22=( 0) s23=( 0) d11=( 0) > s24=( 0) s25=( 0) d12=( 0) > s26=( 0) s27=( 0) d13=( 0) > s28=( 0) s29=( 0) d14=( 0) > s30=( 0) s31=( 0) d15=( 0) > FPSCR: > qemu: uncaught target signal 6 (Aborted) - exiting > note, this only happens with FPC_ARMEL defined. -CfSOFT still works under qemu and my nslu2 (last time i checked). henry ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Initializers on const and var
Hi, is it possible to have an array initialized with variables? I tried sth. like this (by accident, not intentionally): const ctypes: array [0..9] of hid_t = ( H5T_NATIVE_INT, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_NATIVE_HBOOL, H5T_NATIVE_HBOOL ); assuming the names in upper case are constants. But in fact they are variables (declared "cvar; external" but I think that's not the cause of the error). var H5T_NATIVE_INT: hid_t; ... H5T_NATIVE_INT_g : hid_t;cvar;external; initialization H5T_NATIVE_INT := H5T_NATIVE_INT_g; The compiler does find an "illegal expression" after the first item in the initializer. Is there another way but moving the initialization from the interface to the implementation of some "procedure init"? I'd like to see the declaration in the interface part. TIA, Marc ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Built in Query language (or abuse)
A creative idea: procedure Query(trick: Array of Const); begin for i:= CASE // interesting code here end; const SELECT = 1; // token WHERE = 2; // token FROM = 3; // token INSERT = 4; // token begin Query([SELECT, 'foo', FROM, 'bar']) Query([INSERT, INTO, 'bar', WHERE, 'name', '=', 'joe']) end; A database query language built right into the program. Tokens like "SELECT" and "INSERT INTO" could be changed to "SEL" and "PUT" to make it more concise. (I've always found SQL too much like COBOL - large silly reserved words that get in the way). The "array of const" parameters would have to be sorted, tokenized, and possibly some lightly parsed. Handling an "array of const" cleverly means one can still make use of strong typing in pascal. This has some similarities to parameterized queries or TDataset ideas. I've seen other creative suggestions in the fpc community bulletin boards, such as extending the compiler to embed a database query language into it. The disadvantage of extending the compiler is obvious.. it takes time, work, and it takes someone with a brave soul to do it. It adds more bugs to the compiler. http://community.freepascal.org:1/bboards/message?message_id=219521&forum_id=24086#219531 By placing some sort of built in array of const query language into a "module", it means that this special ability of FPC is stored in a library and not in the compiler code base. --Disadvantages of Array of Const Idea-- 1. it is only a theory, I haven't tried it. 2. the abuse factor of it. forgive that for a moment 3. how to handle all the possible errors of bad array of const params 4. reminds me of Lisp, Ruby "domain specific languages" they call them 5. the 'quotes' add some noise here and there Once someone gets a hold of these bag of tricks, they might obfuscate their programs with all sorts of silly hacks, and we might all end up like Paul Graham.. bragging about how FPC is better than all other languages. --Advantages of Array Of Const idea-- A built in mini language would be bound to a real language. Kind of like how fpMake is powered by a real language, and not a poor gnu make style limited language. This analogy isn't quite exactly what I'm trying to get across.. but you might understand what I mean. One has the full power of a strongly typed language.. pascal.. and also his built in mini query language too. Not "either or" as in separate languages! Verbose ugly concatenated SQL strings in our code aren't so type safe..This array of const idea remains type safe and hides details from the programmer. --Another idea-- Remember the "file of Record" innovation in pascal? Table of Record... A "file of record" allows one to remain strongly typed. What about a "DatabaseTable of Record". var // F: File Of DataRec; DB: Table of DataRec; // aka a RelVar begin Connect(DB); Query(DB, SELECT, 'foo', FROM, 'bar'); Close(DB); end; Crazy? Well even Write and WriteLn may have seemed crazy at one time - the revolutionary idea to introduce the "File" and "Text" data types into a language like pascal, instead of sticking with old Algol ideas.. may have seemed crazy. Give it some slack. Files are a poor storage systems for data. Times have changed - people thought up object relational mappers, TDataset, and languages such as Tutorial Dee. So keep an open mind.. and do tell if you have better ideas. I'll mention a URL again: http://community.freepascal.org:1/bboards/message?message_id=219521&forum_id=24086#219531 Daniel and Michael were worried that those ideas from Atanas Atanassov could bastardize the pascal language or the system.pp unit. I would be worried too. Hence why some creative ideas are offered in this email that would place a query language into a module. Or, a new innovation like a File Of Record/Table Of Record type. Someone reading this might even have some better ideas in mind. Tell them if you do! ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
Henry Vermaak schrieb:
Const
+{$ifdef FPC_ABI_EABI}
+ syscall_nr_base = $0;
+{$else FPC_ABI_EABI}
syscall_nr_base = $90;
+{$endif FPC_ABI_EABI}
but i'll confirm in a while.
yes, this works for me.
Fixed in svn.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Initializers on const and var
On Tue, 3 Jun 2008, Marc Santhoff wrote: > Hi, > > is it possible to have an array initialized with variables? > > I tried sth. like this (by accident, not intentionally): > > const > ctypes: array [0..9] of hid_t = > ( > H5T_NATIVE_INT, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_C_S1, > H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_NATIVE_HBOOL, H5T_NATIVE_HBOOL > ); > > assuming the names in upper case are constants. But in fact they are > variables (declared "cvar; external" but I think that's not the cause of > the error). This is the error; The values must be known at compile time. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
Henry Vermaak escribió: yes, this works for me. luca, can you try? Not now (busy at work), later today maybe. -- Luca ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Initializers on const and var
Am Dienstag, den 03.06.2008, 15:41 +0200 schrieb Michael Van Canneyt: > > On Tue, 3 Jun 2008, Marc Santhoff wrote: > > > Hi, > > > > is it possible to have an array initialized with variables? > > > > I tried sth. like this (by accident, not intentionally): > > > > const > > ctypes: array [0..9] of hid_t = > > ( > > H5T_NATIVE_INT, H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_C_S1, > > H5T_C_S1, H5T_C_S1, H5T_C_S1, H5T_NATIVE_HBOOL, H5T_NATIVE_HBOOL > > ); > > > > assuming the names in upper case are constants. But in fact they are > > variables (declared "cvar; external" but I think that's not the cause of > > the error). > > This is the error; The values must be known at compile time. Okay, but that hold true for any kind of variable, not only those "cvar; external;" ones. Anyway, I'll see if changing the base type of the array to pointers is possible. Thanks, Marc ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
En/na Henry Vermaak ha escrit:
2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
2008/6/3 Henry Vermaak <[EMAIL PROTECTED]>:
more info (everything compiled with -dFPC_ARMEL -O- -gl):
[EMAIL PROTECTED]:~/source/armtest$ qemu-arm armtest
Error: Bad syscall: 90004c
qemu: unhandled CPU exception 0x2 - aborting
R00=ffda R01=4007f750 R02=4007f758 R03=
R04=00018ed0 R05= R06= R07=0090004c
ah, it shouldn't add the base number. this might fix it:
Index: sysnr.inc
===
--- sysnr.inc (revision 11178)
+++ sysnr.inc (working copy)
@@ -21,7 +21,11 @@
}
Const
+{$ifdef FPC_ABI_EABI}
+ syscall_nr_base = $0;
+{$else FPC_ABI_EABI}
syscall_nr_base = $90;
+{$endif FPC_ABI_EABI}
but i'll confirm in a while.
yes, this works for me. luca, can you try?
The following program:
program hello;
begin
writeln('hello');
end.
runs but it doesn't print anything, neither under scratchbox nor on the
tablet.
I'm trying to cross-compile the gtk2 example but it seems the compiler
is ignoring -Xd and -Xr:
[EMAIL PROTECTED] fpc-svn]$ compiler/ppcrossarm
-Fupackages/gtk2/units/arm-linux/ -Xd
-Xr/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/
packages/gtk2/examples/helloworld/helloworld.pas
Free Pascal Compiler version 2.3.1 [2008/06/03] for arm
Copyright (c) 1993-2008 by Florian Klaempfl
Target OS: Linux for ARMEL
Compiling packages/gtk2/examples/helloworld/helloworld.pas
Assembling helloworld
Linking packages/gtk2/examples/helloworld/helloworld
/home/luca/crossbinutils/bin/armel-linux-ld: skipping incompatible
/usr/lib/libgobject-2.0.so when searching for -lgobject-2.0
/home/luca/crossbinutils/bin/armel-linux-ld: skipping incompatible
/usr/lib/libgobject-2.0.a when searching for -lgobject-2.0
/home/luca/crossbinutils/bin/armel-linux-ld: cannot find -lgobject-2.0
helloworld.pas(73,49) Error: Error while linking
helloworld.pas(73,49) Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted
[EMAIL PROTECTED] fpc-svn]$ ls
/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/libgobject*
/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/libgobject-2.0.a
/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/libgobject-2.0.la
/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/libgobject-2.0.so@
/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/libgobject-2.0.so.0@
/scratchbox/users/luca/targets/CHINOOK_ARMEL/usr/lib/libgobject-2.0.so.0.1200.12
Bye
--
Luca
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
En/na Luca Olivetti ha escrit:
The following program:
program hello;
begin
writeln('hello');
end.
runs but it doesn't print anything, neither under scratchbox nor on the
tablet.
I installed strace on the tablet:
~ $ strace ./hello
execve("./hello", ["./hello"], [/* 59 vars */]) = 0
syscall: unknown syscall trap 0x8000
Bye
--
Luca
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
En/na Luca Olivetti ha escrit:
En/na Luca Olivetti ha escrit:
En/na Luca Olivetti ha escrit:
The following program:
program hello;
begin
writeln('hello');
end.
runs but it doesn't print anything, neither under scratchbox nor on
the tablet.
I installed strace on the tablet:
~ $ strace ./hello
execve("./hello", ["./hello"], [/* 59 vars */]) = 0
syscall: unknown syscall trap 0x8000
According to here
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=3105/4
the first link should have been
http://wiki.debian.org/ArmEabiPort#head-96054c6cb4209b4a589e645dd50ac0fe133b8ced
and here
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=3105/4
the syscall number should be put in r7
Also the alignment of the parameters in the registers is different.
Of course I cannot make head or tails of syscall.inc, so it's possible
that everything is already done as it should be.
Bye
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
En/na Luca Olivetti ha escrit:
En/na Luca Olivetti ha escrit:
The following program:
program hello;
begin
writeln('hello');
end.
runs but it doesn't print anything, neither under scratchbox nor on
the tablet.
I installed strace on the tablet:
~ $ strace ./hello
execve("./hello", ["./hello"], [/* 59 vars */]) = 0
syscall: unknown syscall trap 0x8000
According to here
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=3105/4
and here
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=3105/4
the syscall number should be put in r7
Also the alignment of the parameters in the registers is different.
Of course I cannot make head or tails of syscall.inc, so it's possible
that everything is already done as it should be.
Bye
--
Luca
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC_ARMEL system calls
2008/6/3 Luca Olivetti <[EMAIL PROTECTED]>: > > the syscall number should be put in r7 > Also the alignment of the parameters in the registers is different. > Of course I cannot make head or tails of syscall.inc, so it's possible that > everything is already done as it should be. mov r7, r0 puts the syscall nr into r7. i haven't looked at the alignment, though :-\ "With EABI, 64-bit function parameters passed in registers are aligned to an even-numbered register instead of using the next available pair." what output does: qemu-arm -strace hello give? (run on your i386 after cross-compiling) did you compile this with the 2.18 binutils? my qemu-arm is happy with my simple hello program. even does writeln(2/3) properly. henry ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] FPC on Palm
Hi, I tried to build a crosscompiler for palmos-arm and palmos-m68k but both failed to compile. Here's the results for m68k make[5]: Entering directory `/home/andrew/programming/fpc/rtl/palmos' /usr/bin/mkdir -p /home/andrew/programming/fpc/rtl/units/m68k-palmos make[5]: *** No rule to make target `m68k/prt0.as', needed by `prt0.o'. Stop. make[5]: Leaving directory `/home/andrew/programming/fpc/rtl/palmos' make[4]: *** [palmos_all] Error 2 make[4]: Leaving directory `/home/andrew/programming/fpc/rtl' make[3]: *** [rtl] Error 2 make[3]: Leaving directory `/home/andrew/programming/fpc/compiler' make[2]: *** [cycle] Error 2 make[2]: Leaving directory `/home/andrew/programming/fpc/compiler' make[1]: *** [compiler_cycle] Error 2 make[1]: Leaving directory `/home/andrew/programming/fpc' make: *** [build-stamp.m68k-palmos] Error 2 and for arm: make[5]: Entering directory `/home/andrew/programming/fpc/rtl/palmos' arm-palmos-as -o /home/andrew/programming/fpc/rtl/units/arm-palmos/prt0.o arm/prt0.as arm/prt0.as: Assembler messages: arm/prt0.as:47: Error: cannot represent BFD_RELOC_RVA relocation in this object file format arm/prt0.as:49: Error: cannot represent BFD_RELOC_RVA relocation in this object file format arm/prt0.as:50: Error: cannot represent BFD_RELOC_RVA relocation in this object file format arm/prt0.as:54: Error: cannot represent BFD_RELOC_RVA relocation in this object file format arm/prt0.as:62: Error: cannot represent BFD_RELOC_RVA relocation in this object file format make[5]: *** [prt0.o] Error 1 make[5]: Leaving directory `/home/andrew/programming/fpc/rtl/palmos' make[4]: *** [palmos_all] Error 2 make[4]: Leaving directory `/home/andrew/programming/fpc/rtl' make[3]: *** [rtl] Error 2 make[3]: Leaving directory `/home/andrew/programming/fpc/compiler' make[2]: *** [cycle] Error 2 make[2]: Leaving directory `/home/andrew/programming/fpc/compiler' make[1]: *** [compiler_cycle] Error 2 make[1]: Leaving directory `/home/andrew/programming/fpc' make: *** [build-stamp.arm-palmos] Error 2 I cant read or write asm but the prt0.as file seems to be copied from the wince dir and it not for palm. Is anyone working with fpc and palm? Regards, Andrew ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: FPC 2.2.1 on Mac OS X
Hi I only noticed now the discussion on the mailing list about fpc 2.2.1 and lazarus on Mac OS X. As the maintainer of the .info files of fpc and lazarus I should probably lay out my ideas about the future. The next step is fpc 2.2.2. It should resolve some of the issues in a clean way and enable to remove some workarounds as well as serve as a solid base for a lazarus installation. When this is settled, I will extend lazarus in the following way: 1) create so-called splitoffs, so there will be separate packages for lazarus-gtk1, lazarus-aqua and when ready lazarus-gtk2. Then the user can simply choose the best interface for his situation. This can be done, whatever the default setting of LCLPLATFORM will be. 2) create double clickable Lazarus applications with links in / Applications/Fink. A remaining question is about the code base I will use for lazarus. The best solution would clearly be that lazarus 0.9.26 comes out shortly before i am ready and so I could base in on that. If not, I would submit versions based on plain 0.9.24 as a first step. Depending on the conditions then, one could consider an intermediate 0.9.25 version. What is the status of the aqua version? Is 0.9.24 good enough at least as a start until 0.9.26 is ready or is it absolutely necessary to include the fixes since 0.9.24? Best wishes - Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
