Re: [fpc-pascal] Any recommendations for a good in-memory storage type

2010-09-28 Thread Zaher Dirkey
On Wed, Sep 22, 2010 at 1:31 PM, Graeme Geldenhuys graemeg.li...@gmail.comwrote: Hi, While implementing drag-n-drop support in fpGUI, I created a TfpgMimeData class. This class will hold various data items, and a mime-type describing each of the data items. Obviously the TfpgMimeData class

Re: [fpc-pascal] Initializing records and other complicated structures

2010-09-28 Thread Jim
On 27-9-2010 13:30, Sven Barth wrote: Am 27.09.2010 10:38, schrieb Honza: 2010/9/27 Jimhakki...@gmail.com: As TIfdTag seems to contain non-pointer records only, I thought I could use Sizeof and tried this: FillByte(tag, SizeOf(tag), 0); //initialize var. The compiler warning doesn't go away

Re: [fpc-pascal] RichMemo in shared SO library - relocation error

2010-09-28 Thread Dibo
You can probably work around the problem for now by going to line 1448 of compiler/ptconst.pas and changing if sym.varspez=vs_const then cursectype:=sec_rodata else cursectype:=sec_data; into cursectype:=sec_data; Hm, it doesn't

Re: [fpc-pascal] Initializing records and other complicated structures

2010-09-28 Thread Jürgen Hestermann
Sven Barth schrieb: It's enough code, because FillByte (and others) are defined with a var parameter and such the hint (not a warning) won't go away. It's an old topic already and we have just to live with it (regarding the Fill* functions). ^^ But why not simply change the definition of the

Re: [fpc-pascal] Initializing records and other complicated structures

2010-09-28 Thread Vincent Snijders
2010/9/28 Jürgen Hestermann juergen.hesterm...@gmx.de: Sven Barth schrieb: It's enough code, because FillByte (and others) are defined with a var parameter and such the hint (not a warning) won't go away. It's an old topic already and we have just to live with it (regarding the Fill*