Re: [fpc-devel] is that intended? private type section in classes versus visibility

2010-08-02 Thread Graeme Geldenhuys
Op 2010-07-30 17:58, Joost van der Sluis het geskryf: > I'm affraid that when the discussion is over, no-one is willing or able > to develop what has been concluded from the discussion. I can only speak for myself. My workflow is as follows... * I see a gap (missing feature) in FPC, Lazarus IDE e

Re: [fpc-devel] threadvar implementation

2010-08-02 Thread Michael Schnell
On 07/30/2010 08:01 PM, Hans-Peter Diettrich wrote: You only have to determine the flat address, before storing it in the pointer variable - @MyThreadvar? How do you think this is possible ? How to you think it's possible in FPC to define a pointer that does not use DS to access the memory lo

Re: [fpc-devel] threadvar implementation

2010-08-02 Thread Michael Schnell
On 07/30/2010 08:01 PM, Hans-Peter Diettrich wrote: The only question is, whether you want the (absolute, flat) address of the threadvar of an *specific* thread, or the address of the threadvar in the *current* thread. Since the current thread can change, the offset of the threadvar record w

Re: [fpc-devel] threadvar implementation

2010-08-02 Thread Michael Schnell
On 07/30/2010 08:01 PM, Hans-Peter Diettrich wrote: Only FS and GS can add an non-zero offset, to the *offset* given in the instruction. The sum of both is the flat "address" (effectively another offset), that can be stored in a pointer variable. In 32/64 bit flat memory models all pointers

Re: [fpc-devel] is that intended? private type section in classes versus visibility

2010-08-02 Thread Marcos Douglas
On Fri, Jul 30, 2010 at 12:58 PM, Joost van der Sluis wrote: > [snip] If people use your time in this thread and this project fails, not to say that these same people would have wasted your time. Maybe it will work, maybe not ... who knows? The same failure could occur in any other thread, don't?

Re: [fpc-devel] threadvar implementation

2010-08-02 Thread Hans-Peter Diettrich
Michael Schnell schrieb: Only FS and GS can add an non-zero offset, to the *offset* given in the instruction. The sum of both is the flat "address" (effectively another offset), that can be stored in a pointer variable. In 32/64 bit flat memory models all pointers are "near", i.e. they don't

Re: [fpc-devel] threadvar implementation

2010-08-02 Thread Hans-Peter Diettrich
Michael Schnell schrieb: You only have to determine the flat address, before storing it in the pointer variable - @MyThreadvar? How do you think this is possible ? How to you think it's possible in FPC to define a pointer that does not use DS to access the memory location ? No need to do so.