Result for 18DB3D1C813FDAE2799BE36DA2DDBAE74BB01619

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-antlr-tool.cm/.cm/x86-unix/ml-antlr-tool.cm
FileSize1110
MD5A564DCB6F6D1C3F5E1FA135314945C21
SHA-118DB3D1C813FDAE2799BE36DA2DDBAE74BB01619
SHA-256948C22044075DA70C2365D8D9496B1330DD734B4FC82125124C7076C79CC76BE
SSDEEP24:tth5O/nIKhddorBhVbwLi8HLnumUZTQoLAnpXb7coRr95jKIt:pUmb1ei8KZTzL8Xb595jH
TLSHT1AE111FAEE77714E2EE63843A02915A1FFB42D008D18392A9BB4116570E2C921267CB6B
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
FileSize482688
MD565F37E1286461EE3BE0422D1EAFAC5AA
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.
PackageMaintainerJames McCoy <jamessan@debian.org>
PackageNameml-lpt
PackageSectiondevel
PackageVersion110.76-2
SHA-12EEBCBF936F867B40D6C6EA1AADB61403737E867
SHA-2567E32162CFC0A07D6FBE23CF251179E03F5B012748BF1A90FA74940D158D11772