Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.comp.lang.pascal > #2

Re: Generic data structures

Path csiph.com!aioe.org!.POSTED!not-for-mail
From "zeLittle " <noreply@noreply.net>
Newsgroups alt.comp.lang.pascal
Subject Re: Generic data structures
Date Tue, 04 Oct 2016 23:51:00 +0200
Organization ZL
Lines 21
Message-ID <op.yotwbaipc5b0tx@mainate> (permalink)
References <20160507163854.84ad1a21bf36c1a99cd7c3d1@gmail.com>
NNTP-Posting-Host K+pBsys+ryhCjRAE2w9KBw.user.gioia.aioe.org
Mime-Version 1.0
Content-Type text/plain; charset=iso-8859-15; format=flowed; delsp=yes
Content-Transfer-Encoding Quoted-Printable
X-Complaints-To abuse@aioe.org
User-Agent Opera Mail/1.0 (Win32)
X-Notice Filtered by postfilter v. 0.8.2
Xref csiph.com alt.comp.lang.pascal:2

Show key headers only | View raw


Le Sat, 07 May 2016 15:38:54 +0200, Anton Shepelev <anton.txt@gmail.com> a  
écrit:

> Number: byte;    { fields here }

Hello, you could replace the field Number with:
o_Data: TDataObject;    { fields here }

So, you'll can carry any type in a TDataObject's public field. Actually,  
the datatype byte is too typed, even compared to a generic pointer.

You could also look to TObjectList: TObject is generic enough to carry all  
what you want.

Regards.

Back to alt.comp.lang.pascal | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Generic data structures Anton Shepelev <anton.txt@gmail.com> - 2016-05-07 16:38 +0300
  Re: Generic data structures "zeLittle " <noreply@noreply.net> - 2016-10-04 23:51 +0200
  Re: Generic data structures "zeLittle " <noreply@noreply.net> - 2016-10-05 00:10 +0200

csiph-web