104 commits

Author	SHA1	Message	Date
Eelco Dolstra	59b94ee18a	* When something goes wrong in the evaluation of a Nix expression, ... print a nice backtrace of the stack, rather than vomiting a gigantic (and useless) aterm on the screen. Example: error: while evaluating file `.../pkgs/system/test.nix': while evaluating attribute `subversion' at `.../pkgs/system/all-packages-generic.nix', line 533: while evaluating function at `.../pkgs/applications/version-management/subversion/default.nix', line 1: assertion failed at `.../pkgs/applications/version-management/subversion/default.nix', line 13 Since the Nix expression language is lazy, the trace may be misleading. The purpose is to provide a hint as to the location of the problem.	2004-04-05 22:27:41 +00:00
Eelco Dolstra	9b44480612	* Use a map to lookup primops. ... * Various performance improvements in the evaluator. * Do not link against unused (and missing!) libraries (-lsglr, etc.).	2004-02-04 16:03:29 +00:00
Eelco Dolstra	c4f7ae4aa5	* Verify that all variables in a Nix expression are defined.	2004-02-03 14:45:34 +00:00
Eelco Dolstra	ac68840e79	* Refactoring: put the Nix expression evaluator in its own library so ... that it can be used by multiple programs.	2003-11-19 11:35:41 +00:00

Renamed from src/nix-instantiate/nixexpr.hh (Browse further)