Result for 01364E71C52F13AB1E406E18C9F6A792AED841F8

Query result

Key Value
FileName./usr/lib/smlnj/bin/.heap/ml-ulex.x86-linux
FileSize1264028
MD53E26F009D9081031804E3977EB654FC5
SHA-101364E71C52F13AB1E406E18C9F6A792AED841F8
SHA-25699536B735247E7796F86E1494CBEF444985A9D4FA35E488E66196A60A2F8AE58
SSDEEP24576:xjrL7PfVxhWiyUpn1I5aFR/xtuvjBrUxWa7qzDql29pL5uFLCzq5k0:9XVxg9I1I5aD/xtubBGWaIpL5uFL0q5f
TLSHT1B845B486AFD361D7E4262070A55EA22F3309F2CB9015C15FF2A84FD6BD3A5603DA9713
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize499272
MD59CC3715D7CE4C25D8AB86DE7F85ED00C
PackageDescriptionSML/NJ language processing tools Tradition has it that when a new programming language is introduced, new scanner and parser generators are written in that language, and generate code for that language. Traditional also has it that the new tools are modeled after the old lex and yacc tools, both in terms of the algorithms used, and often the syntax as well. The language Standard ML is no exception: ml-lex and ml-yacc are the SML incarnations of the old Unix tools. . This package has two new tools, ml-ulex and ml-antlr, that follow tradition in separating scanning from parsing, but break from tradition in their implementation: ml-ulex is based on regular expression derivatives rather than subset-construction, and ml-antlr is based on LL(k) parsing rather than LALR(1) parsing.
PackageMaintainerDebian QA Group <packages@qa.debian.org>
PackageNameml-lpt
PackageSectiondevel
PackageVersion110.79-2+b1
SHA-102F0D783D465151951891EBC420E89221C4E3B41
SHA-2569C60CDBA9CA843227AD4EAEB021E1B49C0BC41F4A532A8436966B12924CCEBB9