Result for 0B473BB8CD8B9C7A149DC8A21DABC8D829262C4E

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-ulex-tool.cm/.cm/x86-unix/ml-ulex-tool.cm
FileSize1113
MD5B05820414498757A2B6268C5BE6D47C5
SHA-10B473BB8CD8B9C7A149DC8A21DABC8D829262C4E
SHA-256C4E97CBC336C8D95EBC48EA05A77D6DE0125042BF721DC663FD55F7023DBE738
SSDEEP24:b0hxnXn76Hqe9xcwDEN9OUu2TQoLAnpXb7coRr95de3:bu2HqAc1u2TzL8Xb595dG
TLSHT1F4217268EB76D02DEC930171B0205E8BBB91C10C908732FBF300AE131E2E20252BCB5B
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
FileSize498750
MD53AC14A175CF52452EAF6741AA75DF364
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-1D77D8DE2FF72448FF49B4CEF39D50F0EA1F37DF6
SHA-25653D81951FB0E8C7C965CACA504ED5359586867A36439D3CAF81854A06ECF0A86