about summary refs log tree commit diff stats
path: root/mu
Commit message (Collapse)AuthorAgeFilesLines
* 4220Kartik K. Agaram2018-03-131-4/+4
|
* 4219 - add an even simpler build scriptKartik K. Agaram2018-03-131-1/+1
|
* 4216 - include simpler alternative to build scriptKartik K. Agaram2018-03-121-1/+1
|
* 4211Kartik K. Agaram2018-02-201-0/+1
| | | | | | | | Just ran into first issue from using the portable /bin/sh rather than a modern shell: https://stackoverflow.com/questions/15744421/read-command-doesnt-wait-for-input Turn on errexit everywhere.
* 4015Kartik K. Agaram2017-10-111-5/+2
|
* 3561Kartik K. Agaram2016-10-221-1/+1
|
* 3468Kartik K. Agaram2016-10-071-1/+1
| | | | Don't run Mu if the compile fails.
* 3447 - drop dependence on GNU makeKartik K. Agaram2016-10-061-6/+1
| | | | | | | | | A generic build system is overkill for such a small project, and it was adding complexity on OpenBSD which doesn't come with GNU make by default. In the process we also eliminate our reliance on bash and perl, at least for the core build script.
* 3442Kartik K. Agaram2016-10-051-2/+6
| | | | | | | | Support for a minimal OpenBSD without bash. Many of the scripts in the repo won't work in that situation, but let's at least make the `mu` script work. I'd like to come up with a clean makefile that doesn't require GNU make.
* 3287 - drop hacky implicit meaning of CXXFLAGSKartik K. Agaram2016-08-311-10/+0
| | | | | | | | | | Now that we have a new build system we shouldn't need to run unoptimized just to save time. (Though that's not strictly true; if a change modifies .build/mu_0.cc which is twice as large as later compilation units, dropping -O3 shaves 10s off the time for an incremental build.) Since we don't need to run unoptimized anymore, let's just explicitly ask for --test-only-app when we need it.
* 3276Kartik K. Agaram2016-08-281-3/+2
|
* 3275Kartik K. Agaram2016-08-281-2/+2
| | | | Follow convention more closely by using CXXFLAGS for C++ files.
* 3170 - multiple --options at the commandlineKartik K. Agaram2016-08-121-2/+4
| | | | | | | | The mu commandline now has four parts: options, commands (of which we only have one so far: 'test'), files/directories and ingredients to pass to 'main'. That cleans up the hacky ordering constraint we had earlier. I've also cleaned up the usage message.
* 3137Kartik K. Agaram2016-07-221-0/+15
| | | | | | | | | | | | | | | | | | Complicated logic to not run core tests. I only want to disable core tests if: a) I'm changing CFLAGS on the commandline (usually to disable optimizations, causing tests to run slower in a debug cycle) b) I'm not printing a help message (either with just 'mu' or 'mu --help') c) I'm loading other files besides just the core. Under these circumstances I only want to run tests in the files explicitly loaded at the commandline. This is all pretty hairy, in spite of my attempts to document it in four different places. I might end up taking it all out the first time I need to run core tests under all these conditions.
* 2994Kartik K. Agaram2016-05-211-1/+1
|
* 1706 - automatically recompile mu when necessaryKartik K. Agaram2015-07-041-0/+8
|
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-27/+0
| | | | I've tried to update the Readme, but there are at least a couple of issues.
* 828 - interactive replKartik K. Agaram2015-02-231-8/+16
| | | | | Still klunky since mu has no notion of a return value. I find myself using $print all the time.
* 407Kartik K. Agaram2014-12-131-0/+3
|
* 405 - permit loading just low levels of codebaseKartik K. Agaram2014-12-131-0/+16
When I'm doing extensive surgery to the internals I want to avoid loading higher levels; they aren't expected to work. But I don't want to keep different levels in separate files just for that. And I definitely don't want to put low-level stuff first. Now I can influence loading in a cross-cutting manner by creating sections with numbers: (section 100 ...code...) And disabling them by running: $ ./anarki/arc 99 mu.arc.t Currently we load all mu 'system software' in level 100, so running at level 99 sidesteps them. Lower levels coming soon. But most of the time we don't need to worry about levels, and the 'mu' script lets us forget about them. Just run .mu files with: $ ./mu factorial.mu To run tests: $ ./mu test mu.arc.t