naggum
naggum copied to clipboard
codingteam
.NET-based lisp for a more civilized age
We need a simple macro evaluation engine. E.g. having a program like ``` (defmacro defmain (body) (list .method "Main" int (list) body) ) (.assembly "dfdf" (defmain (.call Console.WriteLine "ozozoz")) )...
Reflection.Emit is as good start for a codegen engine, but it has its downsides: it requires us to load the assemblies referenced by the generated code in our own process,...
Readme file should include a couple of (not so?) motivating examples.
We aim to produce fully-fledged cross-platform solution, and we already support two common CLI implementations: Windows CLR/.NET and cross-platform Mono. A couple of days ago .NET Core was released, and...
- [Assembler.fs:53](https://github.com/codingteam/naggum/blob/96eae4f9eadcf9b0ce257cc28098bbd60fdb8bb1/Naggum.Assembler/Assembler.fs#L53) - [Program.fs:22](https://github.com/codingteam/naggum/blob/e838e43b01aa51773c654b1665465a2eced27506/Naggum.Assembler/Program.fs#L22) There should be a way to determine output file names for Naggum.Assembler (and also compile either `.exe` or `.dll`).
Because copy-paste programming and code that is more than 10% boilerplate is definitely not cool.
We should integrate the [DLR](https://github.com/IronLanguages/dlr) support into our project. Our attempt to make a statically typed LISP was doomed to failure from the very beginning. Our LISP dialect should be...
Well, there wasn't any activity for a while, but it's time to evolve! I have an idea of implementing the lowest-level self-hosted lisp compiler based on CLR. A base variant...
_(See [Naggum.Test/InstructionTests.fs](https://github.com/codingteam/naggum/pull/39/files#diff-ab898889c230e6089a5b9b875ee5191dR12).)_ We should try to write math (and possibly other) tests with FSCheck.
Whne compiling `Naggum.Interactive`, I see the following warning: ``` C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.CurrentVersion.targets(133,9): warning MSB3884: Could not find rule set file "MinimumRecommendedRules.ruleset". ``` It looks like FXCop message, but we don't...