Hi,
I think this sounds more like "edit distance", but I am not sure why it would
be needed for a config file.
Thank you,
Noah silva
On 2012/04/12, at 4:12, Juha Manninen wrote:
> On Wed, Apr 11, 2012 at 9:19 PM, Mark Morgan Lloyd
> wrote:
> I know that there are algorithms which given
On Wed, Apr 11, 2012 at 9:19 PM, Mark Morgan Lloyd <
markmll.fpc-pas...@telemetry.co.uk> wrote:
> I know that there are algorithms which given a text fragment will find the
> "best fit" from a number of candidates, based on how many substrings have
> to be deleted or changed.
>
> Is there anything
I know that there are algorithms which given a text fragment will find
the "best fit" from a number of candidates, based on how many substrings
have to be deleted or changed.
Is there anything like this in the standard FPC library, and if not does
anybody have one or a URL?
Application is a
Hi,
Two problems here:
1) The documentation is very sparse on this method, and the parameters
and return type are not documented at all
http://www.freepascal.org/docs-html/rtl/classes/readcomponentres.html
2) What's the point of including a "delphi compatibility" method if it
isn't compatibl
Hi Sven en Vincent,
Thanks for your hints. Indeed the dynamic
array was the problem. I have now replaced it by a linked list of
verts/edges/faces. It now works perfectly.
Regards, Darius
On 11 apr
'12, Sven Barth wrote:
> Am 10.04.2012 22:16, schrieb Vincent
Snijders:
>
>> Op 10 april
Vincent Snijders schrieb:
>> type
>> TVertex = record
>>x: double;
>>y: double;
>> end;
>> PVertex = ^TVertex;
>>
>> TEdge = record
>>v1: PVertex;
>>v2: PVertex;
>> end;
.
.
>> Result := @vert_list[vert_count - 1];
>
> I think this is not correct. If you increase the size of
I've developed a small tool to help converting the autogenerated R.java to
Pascal. It's made in a quick and dirty way, but it works. It could be added
to build script to automatically do the conversion before compiling.
It takes 1 command line parameter which is the path to R.java and outputs
the
Am 10.04.2012 22:16, schrieb Vincent Snijders:
Op 10 april 2012 22:06 heeft Darius Blaszyk
het volgende geschreven:
Here's a minimal example that has the bug. First of all the first output is
wrong as it says 0,50 instead of 20,50 (so the x item is overwritten). The
second printed output diffe
