Result for 382DE79592DD3D7C88425952C6DC1B84BAA0C695

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-lpt-lib.cm/.cm/x86-unix/ml-lpt-lib.cm
FileSize53379
MD5BF34B32D20DDAC13B4275E919A177995
SHA-1382DE79592DD3D7C88425952C6DC1B84BAA0C695
SHA-256CF096E935598818925D8E6C1F47ED69D393E0601CBD912BFDA2720EAD156E06F
SSDEEP768:W8lfsWvLM4sOAtKADKHEO8HCWdhdk8QS8PQHqQOtG1oyJNZjawxksDxpA8allcy+:WefRvLRsOAIfkPiMfZTAvd+
TLSHT1F733E6866EC761D3E5352070A10E652F3301F68BE014C26FF2A45BE6FD3A96039AE757
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
FileSize499108
MD576A4A7D51D2D866651F16B6E8D0F2CA1
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-4
SHA-15AB2F8F00F09B4BB567E11ABA8A11D4563E2C91E
SHA-256B4040053618670275AC898934FF933A5A2602CEB20082FC0994CEF4E0D3A2FC9