|Anonymous | Login | Signup for a new account||2013-05-22 19:05 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003725||OCaml||OCaml general||public||2005-07-16 19:04||2006-06-12 22:02|
|Target Version||Fixed in Version|
|Summary||0003725: Ocamldep should search for .mly & .mll files|
|Description||Full_Name: Mike Furr|
Submission from: pcp0010743271pcs.howard01.md.comcast.net (22.214.171.124)
Ocamldep outputs a dependency only for those modules which it can find in the
current search path. However, this search only looks for files ending in .ml or
.mli. Thus if a module uses a lexer or parser defined in a .mll or .mly file,
the dependency will not be shown if these have not yet been compiled into their
respective implementation files. As I typically setup my projects to build
dependencies before any compilation (including that of .mll and .mly files), it
would be nice if ocamldep searched for these file extensions as well.
|Tags||No tags attached.|
I think that .mly and .mll are just one case of a more general problem - people often use various tools for generating the source files. And those tools are often custom to a project and use custom extensions. For example, the Harmony project generates .mly from .srcy.
My proposal would be to have ocamldep take a list of "implementation suffixes" and another list of "interface suffixes" on the command line.
This way ocamldep without any special options would be equivalent to something like
ocamldep -intf .mli -intf .mly -impl .mli -impl .mll -impl .mly
and people with non-standard extensions would be able to add them to the list ("-impl .srcy").
|2005-11-18 10:13||administrator||New Issue|
|2006-06-12 22:02||nogin||Note Added: 0003676|
|2009-08-19 13:20||xclerc||Relationship added||related to 0004519|
|2011-06-06 16:14||xclerc||Relationship added||related to 0005216|
|Copyright © 2000 - 2011 MantisBT Group|