On Thursday 24 February 2011 08:02:20 LacaK wrote:
So also here we can see, that FieldDef.Size is expected to be number of
characters not bytes.
So IMHO logical conclusion will be say, that TFieldDef.Size for string
fields has same menaing as Field.Size, so it is number of characters
(so
On Thu, 24 Feb 2011, LacaK wrote:
Hi,
I am writting here to discuss bug
http://bugs.freepascal.org/view.php?id=17268
(I do not want reopen bug and writte there because I am not sure about my
arguments)
IMHO root of problem is in different definition of TFieldDef.Size and
TField.Size
On Thu, 24 Feb 2011, Martin Schreiber wrote:
On Thursday 24 February 2011 08:02:20 LacaK wrote:
So also here we can see, that FieldDef.Size is expected to be number of
characters not bytes.
So IMHO logical conclusion will be say, that TFieldDef.Size for string
fields has same menaing as
On Thursday 24 February 2011 09:49:51 michael.vancann...@wisa.be wrote:
Agreed. In MSEgui tmsestringfield.size is the maximum allowed character
count for the field. 0 = no limit. tmsebufdataset stores string data as
UnicodeString instead to use a fixed record layout.
But here you
On Thu, 24 Feb 2011, Martin Schreiber wrote:
On Thursday 24 February 2011 09:49:51 michael.vancann...@wisa.be wrote:
Agreed. In MSEgui tmsestringfield.size is the maximum allowed character
count for the field. 0 = no limit. tmsebufdataset stores string data as
UnicodeString instead to use a
On Thursday 24 February 2011 10:16:43 michael.vancann...@wisa.be wrote:
But here you implicitly assume that you have a fixed number of bytes per
character. You should always be explicit about such things, since this
is a non-trivial assumption.
I don't understand.
tmsebufdataset
Hi,
I am writting here to discuss bug
http://bugs.freepascal.org/view.php?id=17268
(I do not want reopen bug and writte there because I am not sure
about my arguments)
IMHO root of problem is in different definition of TFieldDef.Size and
TField.Size
Documentation says, that
1.
On Thu, 24 Feb 2011, Martin Schreiber wrote:
On Thursday 24 February 2011 10:16:43 michael.vancann...@wisa.be wrote:
But here you implicitly assume that you have a fixed number of bytes per
character. You should always be explicit about such things, since this
is a non-trivial assumption.
Please, be patient. I'm working on it, as you can see in the bug reports
and commits.
ok, of course
I did not know your plans, ideas, thoughts etc.
As I said earlier, widestringfields aren't available in fpc yet. Someone
wrote some code for it, but it is never properly tested and probably
On Thu, 2011-02-24 at 12:59 +0100, LacaK wrote:
if you can inform about your plans, order of tasks etc. ... it will be
welcomed
The order.. well, that's difficult.. What comes first, comes first. :)
if I can help you, let me know ... for example I have fix for
TODBCConnection.SetParameters
I'm adding some ftTime tests.
Did you noticed, that I already posted such tests
http://bugs.freepascal.org/view.php?id=18763 ?
Then let me know, I send you fix for ftTime for TODBCConnection ... but
depends on http://bugs.freepascal.org/view.php?id=18773
All widestring-issues are
Hi, I usually compile fpc with make clean all, this builds everything for
RELEASE. How can I compile this with Debug info?
Thanks, in advance,
Leonardo M. Ramé
http://leonardorame.blogspot.com
___
fpc-devel maillist -
On Thu, Feb 24, 2011 at 5:11 PM, Leonardo M. Ramé martinr...@yahoo.com wrote:
Hi, I usually compile fpc with make clean all, this builds everything for
RELEASE. How can I compile this with Debug info?
make clean all OPT=params_here
Like this:
Thanks Marcos, I used make clean all OPT=-g and aparently it didn't include
debugging info. How can I check that?
Leonardo M. Ramé
http://leonardorame.blogspot.com
--- On Thu, 2/24/11, Marcos Douglas m...@delfire.net wrote:
From: Marcos Douglas m...@delfire.net
Subject: Re: [fpc-devel]
On 24 February 2011 20:56, Leonardo M. Ramé martinr...@yahoo.com wrote:
Thanks Marcos, I used make clean all OPT=-g and aparently it didn't include
debugging info. How can I check that?
Try OPT=-gl -O-. You can check the .o files with the file
command. This will tell you if it's stripped or
Thanks, now I can debug fpc packages!.
Leonardo M. Ramé
http://leonardorame.blogspot.com
--- On Thu, 2/24/11, Henry Vermaak henry.verm...@gmail.com wrote:
From: Henry Vermaak henry.verm...@gmail.com
Subject: Re: [fpc-devel] Compiling FPC with Debug info
To: FPC developers' list
On Thu, Feb 24, 2011 at 7:52 PM, Leonardo M. Ramé martinr...@yahoo.com wrote:
Thanks, now I can debug fpc packages!.
Very good!
I did not answer your another question because Henry did.
Marcos Douglas
___
fpc-devel maillist -
17 matches
Mail list logo
