On 21/01/14 18:42, waldo kitty wrote:
> On 1/21/2014 10:21 AM, Mattias Gaertner wrote:
>> On Tue, 21 Jan 2014 09:51:38 -0500
>> waldo kitty wrote:
>>
>>> On 1/18/2014 7:40 PM, waldo kitty wrote:
what is the best method of coding a decision tree with options that have
three
sta
FPC trunk x86, windows.
Warning: fiddling newb alert.
I have a unit httpclient that apparently uses winsock2:
3rdparty\httpclient.pas(0,0) Fatal: Can not find unit WinSock2 used by
Sockets.
Temporarily adding this to the other unit files (-Fu) in Lazarus
;$(fpcsrcdir)\packages\rtl-extra\src\win
On 1/22/2014 3:52 AM, Lukasz Sokol wrote:
[...]
^and this...
looks like a (good?) use for a dynamic array of TMinMaxState = [mmNone, mmMin,
mmMinMax, mmMax];
(then var Options = array[static or dynamic] of TMinMaxState;)
This assumes options have a fixed position in the array however... but the
Am 22.01.2014 16:13, schrieb Reinier Olislagers:
FPC trunk x86, windows.
Warning: fiddling newb alert.
I have a unit httpclient that apparently uses winsock2:
3rdparty\httpclient.pas(0,0) Fatal: Can not find unit WinSock2 used by
Sockets.
Temporarily adding this to the other unit files (-Fu) i
On 22/01/2014 17:05, Sven Barth wrote:
> Am 22.01.2014 16:13, schrieb Reinier Olislagers:
>> Does the FPC make files need some more adjustments... or do I need to
>> make them ;)
> Should now be fixed in revision 26564. :)
>
Thanks a lot Sven, works perfectly!
___
On 22/01/14 15:51, waldo kitty wrote:
> On 1/22/2014 3:52 AM, Lukasz Sokol wrote:
> [...]
>> ^and this...
>> looks like a (good?) use for a dynamic array of TMinMaxState = [mmNone,
>> mmMin, mmMinMax, mmMax];
>> (then var Options = array[static or dynamic] of TMinMaxState;)
>>
>> This assumes opti
Am 2014-01-22 07:41, schrieb leledumbo:
Jürgen Hestermann wrote
Realy?
But why that?
It cannot be negative.
Using integer instead of unsigned values reduces the possible (positive)
range
and produces such illogical (to me) compiler warnings.
Delphi compatibility and maximum data size limitatio
Am 22.01.2014 19:00, schrieb Jürgen Hestermann:
>
> Am 2014-01-22 07:41, schrieb leledumbo:
>> Jürgen Hestermann wrote
>>> Realy?
>>> But why that?
>>> It cannot be negative.
>>> Using integer instead of unsigned values reduces the possible (positive)
>>> range
>>> and produces such illogical (to
On 22.01.2014 19:00, Jürgen Hestermann wrote:
Am 2014-01-22 07:41, schrieb leledumbo:
Jürgen Hestermann wrote
Realy?
But why that?
It cannot be negative.
Using integer instead of unsigned values reduces the possible (positive)
range
and produces such illogical (to me) compiler warnings.
Delph
On 1/22/2014 12:12 PM, Lukasz Sokol wrote:
[...]
If you insist on using bits define them:
it isn't that i'm insisting on using them... more the way that my linear mind
sees them... i'm trying to change this if it affords me better code that is
easier to read, understand and modify...
c
On 1/22/2014 1:00 PM, Jürgen Hestermann wrote:
Am 2014-01-22 07:41, schrieb leledumbo:
Jürgen Hestermann wrote
Realy?
But why that?
It cannot be negative.
Using integer instead of unsigned values reduces the possible (positive)
range
and produces such illogical (to me) compiler warnings.
Delp
2014/1/22 waldo kitty
> the string type is/was a 256 character array with the 0th (zero-th)
> element containing the length of the string... this allowed one to
> immediately know how many characters to read at once... it was much faster
> than iterating thru the array looking for a nul byte as d
On 1/22/2014 5:39 PM, Frederic Da Vitoria wrote:
2014/1/22 waldo kitty mailto:wkitt...@windstream.net>>
the string type is/was a 256 character array with the 0th (zero-th) element
containing the length of the string... this allowed one to immediately know
how many characters to read
13 matches
Mail list logo
