Result for 1732D3D8543E5E5E3A913E04698D2DA0FC04EB0A

Query result

Key Value
FileName./usr/lib/smlnj/bin/.heap/ml-antlr.x86-linux
FileSize1057060
MD5E0044EA194086849D662C26BD5D67A9E
SHA-11732D3D8543E5E5E3A913E04698D2DA0FC04EB0A
SHA-256567D4993D93459B3E0AC1B44BE5C4BA3D83133E123982D92E9A625D797B364DE
SSDEEP24576:iiBzdocSyakcl1cfIUcvkxb17mpaJEdI:ikzacSfkfNcsN1tO
TLSHT1E2259387AFD761C7E4262070655E922F3309F28BA015C56FF2A44FD6FD3A5603CAA613
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