Result for 1B9BC3FC8B11C06D73213E491F6857BA0C4B1ABC

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-lpt-lib.cm/.cm/x86-unix/ml-lpt-lib.cm
FileSize53393
MD5BB0B731DE237B2A1AEAC6E6B4B43E66C
SHA-11B9BC3FC8B11C06D73213E491F6857BA0C4B1ABC
SHA-256EBD710FDAC3D10745E2EBDAFAB92AC671D9AEF6EBA4371E02482C7AA1ED977EE
SSDEEP768:u0UWGKZs8sH8v6T2EVhw83Z5kS8PQHqQOtG1oyJNZjawxkKD9XA8gY4rp0:5UWGZfxVKMfZfAPr+
TLSHT15033D68A6EC761C3E5392070A11E652F3301F28BE415C26FF6941BE6FD3E95039AA717
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
FileSize498462
MD583F6938C298899CCFEBB10E51A669856
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-1550ED85F50E0D7B8092CF124902F669567C11ACD
SHA-256F9C4F0707A3A012AB8E4828882CD710D959432E759C7E146174F1518CB27CC00