On 03/18/2015 05:36 PM, Tony Whyman wrote:
TDataEvent = procedure (Data: PtrInt) of object;
To me PtrUInt seems more appropriate.
-Michael
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Based on what the documentation says introduction of ptrint type was a
mistake, shouldn't the PtrInt type be marked as deprecated in FPC 3.0.0
and removed in a later release like 3.0.2 or 3.2.0?
http://www.freepascal.org/docs-html/rtl/system/ptrint.html
Regards,
- Graeme -
--
fpGUI Toolkit
Hmmm, PtrInt is used in that very useful method TApplication.QueueAsync
Call. Could cause a lot of problems in Lazarus apps if it was removed
now - or at least without a lot of planning and warning.
http://lazarus-ccr.sourceforge.net/docs/lcl/forms/tapplication.queueasynccall.html
On 18/03/15
On 2015-03-18 15:01, Mattias Gaertner wrote:
TList stores arbitrary Pointers. To store an arbitrary integer you cast
it with PtrInt. Is there an integer list?
Generics? [warning: I know nothing about generics]
Good point either way - thanks for the example.
Regards,
- Graeme -
--
fpGUI
On Wed, 18 Mar 2015, Nikolay Nikolov wrote:
On 18.3.2015 г. 16:53, Graeme Geldenhuys wrote:
Based on what the documentation says introduction of ptrint type was a
mistake, shouldn't the PtrInt type be marked as deprecated in FPC 3.0.0
and removed in a later release like 3.0.2 or 3.2.0?
On Wed, 18 Mar 2015 14:53:50 +
Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote:
Based on what the documentation says introduction of ptrint type was a
mistake, shouldn't the PtrInt type be marked as deprecated in FPC 3.0.0
and removed in a later release like 3.0.2 or 3.2.0?
On 18.3.2015 г. 16:53, Graeme Geldenhuys wrote:
Based on what the documentation says introduction of ptrint type was a
mistake, shouldn't the PtrInt type be marked as deprecated in FPC 3.0.0
and removed in a later release like 3.0.2 or 3.2.0?
On 2015-03-18 15:38, Tony Whyman wrote:
problem is not whether or not the parameter should be PtrInt or PtrUint,
it is currently PtrInt and changing it means a lot of work for any
application that uses it.
If the data you pass in is always positive pointer addresses (I would
assume this
Mattias Gaertner wrote on Wed, 18 Mar 2015:
On Wed, 18 Mar 2015 14:53:50 +
Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote:
Based on what the documentation says introduction of ptrint type was a
mistake, shouldn't the PtrInt type be marked as deprecated in FPC 3.0.0
and removed in
On Wed, 18 Mar 2015 15:29:14 +
Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote:
On 2015-03-18 15:23, Tony Whyman wrote:
PtrInt is used in that very useful method TApplication.QueueAsync
Call.
Though I never used the QueueAsync() call myself, but looking at the
declaration,
QueueAsyncCall takes two arguments - a pointer to a method and data.
The method declaration must be of the type:
TDataEvent = procedure (Data: PtrInt) of object;
My apps have loads of methods defined as above and would certainly fail
to compile if the PtrInt type was replaced with Ptruint.
On 2015-03-18 15:23, Tony Whyman wrote:
PtrInt is used in that very useful method TApplication.QueueAsync
Call.
Though I never used the QueueAsync() call myself, but looking at the
declaration, shouldn't that data type be PtrUInt anyway? As far as I
understand Data points to data in memory,
It's one I tend to use a lot as it's a nice platform independent way
scheduling processing in the next cycle round the message loop. The
problem is not whether or not the parameter should be PtrInt or PtrUint,
it is currently PtrInt and changing it means a lot of work for any
application that
13 matches
Mail list logo
