| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
Better warning if I try:
mu test --test-only-app sandbox
instead of:
mu --test-only-app test sandbox
|
|
|
|
|
|
|
| |
Ugly that we didn't need 'screen' to provide a type in scenarios
(because assume-screen expands to a definition of 'screen') but we did
need a type for 'console'. Just never require types for special names in
scenarios.
|
|
|
|
| |
Fix CI. Turns out strlcpy and strlcat are not implemented on Linux.
|
|
|
|
| |
Fix some OpenBSD warnings.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Drop an ancient case of premature optimization: skipping transform for
recipes without bodies. These days recipes also have headers that need
transforming.
Thanks Caleb Couch for running into this issue.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Improvements to syntax highlighting, particularly for Mu code in C++
files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A long-standing problem has been that I couldn't spread code across
'run' blocks because they were separate scopes, so I've ended up making
them effectively comments. Running code inside a 'run' block is
identical in every way to simply running the code directly. The 'run'
block is merely a visual aid to separate setup from the component under
test.
In the process I've also standardized all Mu scenarios to always run in
a local scope, and only use (raw) numeric addresses for values they want
to check later.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Stop checking the number of ingredients and products when picking
shape-shifting recipes. That's more consistent with how we handle
regular recipes, and we still get errors in all the examples I can think
of:
reverse # no ingredients or products
n:num <- length # no ingredients; products don't provide type
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Clean up a memory leak and a couple of other things.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Support reloading the recipe side of the edit/ app when it includes type
abbreviations.
Thanks Ella Couch for reporting this problem.
|
| |
|
| |
|
|
|
|
| |
Avoid spurious mutability errors due to index variables.
|
| |
|
| |
|
|
|
|
|
| |
Wrap $read-from-socket in a channel and fix the socket example
so that browser's display the response properly.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Undo commit 3340. Let's standardize names of non-core files to only have
dashes. That's also consistent with the edit/ and sandbox/ apps. Mu
programmers will tend to pervasively use dashes, just like Lisp
programmers.
Scripts will continue to use underscores..
|
|
|
|
|
|
|
| |
$write-to-socket, $read-from-socket, and $accept now pass around
references to socket pointers.
$read-from-socket handles EOF explicitly.
|