Result for 2F09C2D390B947C082C5536C199B4160B3F38624

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-antlr-tool.cm/.cm/x86-unix/ml-antlr-tool.cm
FileSize1110
MD5A23C32FD62526C1BCDA4277730167235
SHA-12F09C2D390B947C082C5536C199B4160B3F38624
SHA-256C4F0CDA30E752253BB9522639A706A66E02E833E343EAD3DE1BDC2BE718AE879
SSDEEP24:zEth5O/nmHKhddoqhSnVbhtdTcQUZTQoLapXb7coRr95jKIt:aHUmGI179cZZTzLkXb595jH
TLSHT1D511426DEB33D9B5DCA3143540914A1EFB46D404D1C762F6BB0007A3086DA16343CAAB
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