[Seqan-dev] Suffix tree incorrect behaviour bug in seqan 1.2


Hi,

Ticket 292 describes a case where a suffix tree in release 1.2 of seqan does not behave as expected. Does anyone know if this has been fixed in a later version of seqan in svn? A bug (# 93) with similar symptoms was fixed in revision 4875. Was revision 4875 made before or after release 1.2?

http://trac.mi.fu-berlin.de/seqan/ticket/292
http://trac.mi.fu-berlin.de/seqan/ticket/93

Thanks,
John.