Result for 113788A141D5FC180EF62C78FC3B5AFCA5017B24

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-lpt-lib.cm/.cm/x86-unix/ml-lpt-lib.cm
FileSize53310
MD5E54F7148F7294246477DFCA7B331A95F
SHA-1113788A141D5FC180EF62C78FC3B5AFCA5017B24
SHA-256CC3FD6FD7B8C987D753D8033948E9E0DA480D40F9A661E39D3B6E855667A7102
SSDEEP768:NJJXtvtUVPDi3udL5/thYM3ZKozSy6d1kqGtz1kJxebudz5Qk9fD95A80Q9tp0:3ptKPTz/Oes5jAC+
TLSHT13933D59B6ED361D3E4392070A11E512F7305F28BA005C26FF2941BE6FD3A96039AE717
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
FileSize494816
MD5774DDA8AE1CD84260FECA8FA4E4C663B
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameml-lpt
PackageSectiondevel
PackageVersion110.79-4
SHA-1DCC7172C4C0E9332B3B8052A17C5945C286595B4
SHA-256CEEAD71FBB23331008FA61ED6284766F2191819C9D7E30291E09BBF91AACAB38