Result for 164BF7669B13CC924E5A859626D846C9F0FA15E6

Query result

Key Value
FileName./usr/lib/smlnj/bin/.heap/ml-ulex.x86-linux
FileSize1233300
MD5F9B2708F9506C6582A11CE2563743CC8
SHA-1164BF7669B13CC924E5A859626D846C9F0FA15E6
SHA-2563C7A928BCB866FFD70E7580BBB4224909485E38FF096ECE651F24275D7B51CE3
SSDEEP24576:MBJBB7ddxVxWSfLWkcl1cfIU7v9Oo5Qks/iQbSM3mpTYvsD2wdq:mBrxVxWSfSkfN7FOo5QN/iQbbVED2Iq
TLSHT18945B496AFD360C7E4262070A56DA22F3349F2CB9014D56FF2A44FD6FD3A5503CAA613
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