Result for 0340B0AEB9223DDF972283FFEDCD207CA2809804

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-lpt-lib.cm/.cm/x86-unix/ml-lpt-lib.cm
FileSize51066
MD523957ADC207D3CBDAD91D9CA7CA566D6
SHA-10340B0AEB9223DDF972283FFEDCD207CA2809804
SHA-256C1ED786B41DE228FA88BF6BC21789A13F93E6C3F857AC8535AF5815D1E44A780
SSDEEP768:qAElivnPX01IyIp0ZVhw83ZQUWd0hIs4UTXQWhVcLh2S2H8bg+arhp0:qAEliv/33IhWfWhscHD+aN+
TLSHT14E33D89A6FC351C3E93A6070B11E612F3305F28AE415C1AFF2941BE6BD3A5513DAA713
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