Result for 1EF19AF1085484D1912F0FC55E1D76AB899644CC

Query result

Key Value
FileName./usr/lib/smlnj/lib/ml-lpt-lib.cm/.cm/x86-unix/ml-lpt-lib.cm
FileSize53132
MD5CEB2C2CF266B3117DAE7F2870C075502
SHA-11EF19AF1085484D1912F0FC55E1D76AB899644CC
SHA-2563153BFAA288FB730CCD8B19A0D1FC802AB9E9FD0BF969F6303938CE2CB278949
SSDEEP768:YVBtfZLfHkX0xIyIp0MthYM3ZsKwyhOuElP6XWpVO0oD95A8Ellctp0:8BtJPoT3ZXw27WpKAhy+
TLSHT18A33E7976EC761D3E5362070A11E612F7301F28BE015C26FF2945BE6FD3A56039AA713
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
CRC327B373A66
FileName54847
FileSize486870
MD53EE8BC5BB6FC342435AD9D96BB996648
OpSystemCode362
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.78-2
ProductCode184819
RDS:package_id184819
SHA-17BF7D022D128B62A04AE0A9341CACA15F6DDAA3D
SHA-2561A8B2392C30556D4E2332F02D6A4A76D80C5966CBD9EB40F9C654569A2658CD0
SpecialCode
dbnsrl_legacy
insert-timestamp1648719972.7769434
sourceRDS_2022.03.1_legacy.db