RE : Re: [text] Longest common subsequence wrong result?

2017-03-31 Thread Sébastien Piller
should have been clearer in the documentation. Do let me know if you think there’s a way to better present this details. Many thanks and all the best, -Rob > On Mar 31, 2017, at 7:16 AM, Sébastien Piller <m...@sebpiller.ch> wrote: > > Hi all, > If I call > new LongestCommo

[text] Longest common subsequence wrong result?

2017-03-31 Thread Sébastien Piller
Hi all, If I call new LongestCommonSubsequence ().apply ("xxx","yyy") I get 0 (correct) If I call  new LongestCommonSubsequence ().apply ("Gandalf","Sauron") I get 2 which looks incorrect to me (should have got 1 since there is no sequence of 2 chars on both strings. Is it a bug or an expected

RE : Re: [text] Longest common subsequence wrong result?

2017-03-31 Thread Sébastien Piller
t : Re: [text] Longest common subsequence wrong result? Sébastien Piller wrote: > Hi all, > If I call > new LongestCommonSubsequence ().apply ("xxx","yyy") > I get 0 (correct) > If I call > new LongestCommonSubsequence ().apply ("Gandalf",&q