Result for 2CDC6C7D984B0613BE8A384E7D1F671C324CE44D

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-antlr-tool.cm/.cm/x86-unix/ml-antlr-tool.cm
FileSize1120
MD524986DB363EA74F1E19CFF9B6C2441DD
SHA-12CDC6C7D984B0613BE8A384E7D1F671C324CE44D
SHA-25672E9BAD0267523FED6FEE71AEB4887A5EB724C913222517E96C2216EB2B4E9CA
SSDEEP24:YPbGh5gnAnRKhdzF/9ijktmDDbYW9itOUZTQoLAnpXb7coRr95jKIt:YPbyUzF/9qvLL94ZTzL8Xb595jH
TLSHT15A2142ECEB7B14E6D87305B96021CF0DDB91D008D4C721A9F70009D30C99A28547CB9B
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
FileSize499236
MD56304C4C1C0825433A94DFA6B8E28C8E3
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-6
SHA-15D68E2D7C2A4A7E785BF50AE1B0A1C1E70889FE0
SHA-256A3F6AB8B27BE7809CA63F3858C67C3C8161269E15D0E1CB7D7DC18F0F5874F41