> Hello,
>
> Exceptions like the name suggested, is to mark something that you are not
> suppose to expect.
> For example while getting a data something went wrong, like disconnection,
> wrong size of data etc...
>
> The usage of exception is very costly in performance, and there for should
> use o
>
>
> On Fri, 16 Dec 2011, dhkblas...@zeelandnet.nl wrote:
>
>>
>> On implementing a linked list I hit to some unexpected (doesn't mean
>> incorrect though) behaviour.
>>
>>
>>
>> ptest = ^test;
>> test = record
>> p: pointer;
>> end;
>>
>>
>>
>> new(mytest);
>>
>>
>>
>> When I a
>
> On 12 Dec 2011, at 19:56, nore...@z505.com wrote:
>
>> procedure proc1; stdcall;
>> begin
>> writeln('hello');
>> end; exports proc1;
>>
>> procedure proc2; stdcall;
>> begin
>> writeln('hello 2');
>> end; exports proc2;
>>
>>
>> end.
>>
>>
>> Notice how I put exports in several places...
>>
>
>>
>>
>> Well maybe ExportAll compiler feature should be suggested?
>>
>> But please try this
>>
>> unit Unit1;
>>
>> {$mode objfpc}{$H+}
>>
>> interface
>>
>> procedure proc1; stdcall;
>> procedure proc2; stdcall;
>>
>> implementation
>>
>>
>> procedure proc1; stdcall;
>> begin
>>writeln('he
> On 2011-12-12 00:48, nore...@z505.com wrote:
>>
>>> Ok, thanks for clearifying that. I guess it's going to be a lot of
>>> include files instead... :)
>>>
>>> -Torsten.
>>
>>
>> Why do you need include files in your case?
>> You can put the units in the uses clause of your library.
> Because it i
> Ok, thanks for clearifying that. I guess it's going to be a lot of
> include files instead... :)
>
> -Torsten.
Why do you need include files in your case?
You can put the units in the uses clause of your library.
library something;
uses
someunit;
exports
someunit.yourproc;
end.
The so
> Hi.
>
> I'm trying to create a shared library (under linux) and I not sure what
> the
> difference between the modifier *export* and the section *exports* is?
> Or perhaps
> when to use one and the other...
Just different ways of doing it.
You can export each one, or you can use exports clause
I wrote:
>
> I think I found some documentation that still doesn't include
> CloseThread in the examples.. I will send patches or recommendations to
> the documentation soon. For example closethread is now documented as a
> function, but some of the other pages that show threading examples just
>
>> The usual answer for this question is libreadline. I already worked with
>> it (in plain C) but before I do a header translation for FreePascal I
>> wanted to ask you for your opinion if there is a better alternative or
>> anybody already has a header translation or even programmer-friendly
>> w
> On 9 December 2011 09:47, Florian Klaempfl wrote:
>>
>> According to measurements of me and other peoples, random is only 7-10
>> times slower (depending on the CPU).
>
> What do you feed your computer, because mine differs vastly from yours.
>
In europe electricity is sometimes 220 volts. Twice
> On 28.11.2011 21:25, nore...@z505.com wrote:
>>> Am 14.11.2011 02:32, schrieb nore...@z505.com:
First I thought I would post this to the mailing list to ask you what
the
proper way to program with threads is. If we must call closethread on
MS
Win machines but not unix mac
> 2011/5/1 Johann Glaser :
>
>> If you find any improvements or comments don't hesitate to send me an
>> EMail.
>
> I just used it. I only needed readline() and add_history(), these two
> functions are already enough to make a ReadLn() substitute that really
> works and It works like a charm! Thank
> Am 14.11.2011 02:32, schrieb nore...@z505.com:
>> First I thought I would post this to the mailing list to ask you what
>> the
>> proper way to program with threads is. If we must call closethread on MS
>> Win machines but not unix machines, then something needs to change to
>> make
>> the thread
While testing an updated version of nYume (aservia) I found that the
program is leaking thread handles on Ms Windows. The program uses
BeginThread and EndThread calls.
However, when I add CloseThread() right before EndThread(, the program no
longer leaks handles. So, CloseThread may be needed on M
>
>
> On Wed, 9 Nov 2011, Graeme Geldenhuys wrote:
>
>> On 9 November 2011 10:40, wrote:
>>> It definitely works, I also use it in a commercial project to implement
>>> full-text-search on a firebird database.
>>
>>
>> Now that would be pretty awesome! :)
>
> It is.
> When I showed it to the cust
>
>
> On Tue, 8 Nov 2011, nore...@z505.com wrote:
>
>> Has anyone got Ioda 1.3 fulltext search project working?
>
> I have it working.
>
Good. I got 1.2 working recently and had to edit the Config file and set
fileref to 1 for it to work I think.
So you have 1.3 working? whereas only 1.2 worked f
Has anyone got Ioda 1.3 fulltext search project working?
Every time I try version 1.3 it doesn't seem to find any words in a file
that is indexed when I try a simple demo with it.
The project IODA is here: http://sourceforge.net/projects/ioda/files/
I make some sample files as follows:
words.tx
101 - 117 of 117 matches
Mail list logo
