Difference between revisions of "Wishlist"
Bas Lijnse (talk | contribs) (Added a short intention statement about this page.) |
Bas Lijnse (talk | contribs) (Added improved import wish) |
||
| Line 1: | Line 1: | ||
Clean is a continuous work in progress. If you have any ideas about what is missing in Clean or could be improved you can add them to this page. | Clean is a continuous work in progress. If you have any ideas about what is missing in Clean or could be improved you can add them to this page. | ||
Adding something to the wishlist does '''not''' automatically mean that your great idea will be added to Clean. This list is just a place to collect ideas about how Clean could be improved. | Adding something to the wishlist does '''not''' automatically mean that your great idea will be added to Clean. This list is just a place to collect ideas about how Clean could be improved. | ||
| + | |||
| + | |||
| + | == Improved imports == | ||
| + | I would like to see an improvement import system for modules which would allow hierarchic package names and qualified imports. When for example a definition module ''Baz.dcl'' in a directory ''foo/bar'' could be imported using the statement ''import qualified foo.bar.Baz'', it becomes possible to create a large hierarchic repository of libraries without namespace conflicts. As additional advantage, you no longer need to supply multiple paths in project or environment files. | ||
| + | |||
| + | --[[User:Bas Lijnse|Bas Lijnse]] 14:11, 31 March 2008 (CEST) | ||
Revision as of 13:11, 31 March 2008
Clean is a continuous work in progress. If you have any ideas about what is missing in Clean or could be improved you can add them to this page. Adding something to the wishlist does not automatically mean that your great idea will be added to Clean. This list is just a place to collect ideas about how Clean could be improved.
Improved imports
I would like to see an improvement import system for modules which would allow hierarchic package names and qualified imports. When for example a definition module Baz.dcl in a directory foo/bar could be imported using the statement import qualified foo.bar.Baz, it becomes possible to create a large hierarchic repository of libraries without namespace conflicts. As additional advantage, you no longer need to supply multiple paths in project or environment files.
--Bas Lijnse 14:11, 31 March 2008 (CEST)
