Result for 08A28166EEF101DD610316F4AF7A3CFB17A267E1

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-lpt-lib.cm/.cm/x86-unix/ml-lpt-lib.cm
FileSize51175
MD5518451DC69DB4FF8114FA42A6476E6C1
SHA-108A28166EEF101DD610316F4AF7A3CFB17A267E1
SHA-256EE9D63F68FFB2AA2B28F07DF5C6298CAF36FADDFA8428B868892638A1330A265
SSDEEP768:/2hAMkOJ0qPl8v6T2HthYM3ZFKwyhOuElP6XWpVO0ED95A8bbT+Rp0:/2hAMkOT7uOw27WpKAYb0+
TLSHT1C633D79B6FD361D3E53960B0A20E511F7705F28BE025C1AFF2940BE6BD3A55039AA713
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
FileSize482962
MD53D7DB1F7C823BB17F99A2D2ADA56540D
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-176F137860F9D76A7B5329E7BA9430913CC6AC9C2
SHA-256301EBEF30C7AD440F6410117EDB444C68F728732FA310D4E80A83AE1C6E9EF11