Result for 24B1B4A5FAB2A49408489926F70CB8BE8F525FB8

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-antlr-tool.cm/.cm/x86-unix/ml-antlr-tool.cm
FileSize1120
MD564FFAA397E469ABB7CF69E9C6D97D436
SHA-124B1B4A5FAB2A49408489926F70CB8BE8F525FB8
SHA-256C06CDFD951BC4A86D890B1768065B468C9A1D333E4152CC2FA6EC552CADD0C00
SSDEEP24:GGh5gn+LLmRKhdzReijUnHbDbb3CmvVUn9UZTQoLAnpXb7coRr95jKIt:GI/wUzReqwHDGNmZTzL8Xb595jH
TLSHT13821122CDBBB18B3E96314345061DA1EEB81D019D48322BCFB01166208ACD2501BDB9B
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