Result for 00F50AA93016217F1BA67E87C2A07AD61CDF57CB

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-ulex-tool.cm/.cm/x86-unix/ml-ulex-tool.cm
FileSize1097
MD5EBAB977AC53CDAE092A72704E3276A46
SHA-100F50AA93016217F1BA67E87C2A07AD61CDF57CB
SHA-256B4CE14756801B24EE65476F4C0C00FC433D4DC6FF996CFF66AEE4F5E6E506D8D
SSDEEP24:6Vhhn+a76amyO3HVfFq93xU7ZUu2TQoLapXb7coRr95de3:7a2tRHdFecqu2TzLkXb595dG
TLSHT1DC111FACAB7660ADED130136B2104B09BF85E2CD929726FEE70046670D2D15421BDFAA
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
FileSize876964
MD536505982807B42B3D3F76D964D08D6C9
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.76-1
SHA-1724089FE544F936B1E24B98511FCC6798FAA78DA
SHA-256A36030D2DDFBD0F12A78183EC9BACA1815CF107017FA0BC73981E563EC7FAD8D