Nim - This repository contains the Nim compiler, Nim's stdlib, tools, and documentation. (mirror)

	Commit message (Expand)	Author	Age	Files	Lines
*	added encodings stdlib	Araq	2011-06-16	1	-0/+1
*	tuple unpacking is not enforced in for loops anymore	Araq	2011-06-15	1	-0/+1
*	bugfix: endless loop in parser; added sphinx wrapper	Araq	2011-06-14	1	-0/+1
*	intsets are now a proper module and part of the stdlib	Araq	2011-06-14	1	-0/+1
*	basic generic collections implemented and tested	Araq	2011-06-07	1	-0/+3
*	threads clean up their heap	Araq	2011-06-04	1	-0/+2
*	first steps to thread local heaps	Araq	2011-06-02	1	-1/+3
*	further steps for thread support; bootstrapping should require unzip C source...	Araq	2011-05-16	1	-0/+1
*	deprecated system.copy: use system.substr instead	Araq	2011-05-14	1	-0/+1
*	newStringOfCap implemented and used to optimize some procs	Araq	2011-05-08	1	-1/+2
*	C source regenerated	Araq	2011-04-24	1	-0/+2
*	hashtables: 1st version; parseutils additions	Araq	2011-04-18	1	-0/+1
*	p[] instead of p^	Araq	2011-04-11	1	-0/+4
*	added another system.open; bugfix: koch clean may not break .git dirs anymore	Araq	2011-04-03	1	-1/+2
*	added 'reset' news entry; fixed #23	Araq	2011-03-25	1	-0/+1
*	bugfixes; field discriminant checks; linearScanEnd, unroll, shallow pragmas	Araq	2011-03-23	1	-1/+1
*	linearScanEnd pragma; string case statement optimization	Araq	2011-03-14	1	-1/+5
*	distinction between re.replace and re.replacef; speed improvements for re module	Araq	2011-03-06	1	-1/+2
*	tests themselves contain the expected result	Araq	2011-02-20	1	-0/+2
*	REPL improvements	Araq	2011-02-13	1	-4/+4
*	non-nil AST; continue after errors for IDE support	Araq	2011-02-12	1	-0/+1
*	changed handling of generalized string literals	Araq	2011-02-07	1	-0/+2
*	nimgrep --ext support	Araq	2011-02-02	1	-0/+4
*	nimgrep: first working version	Araq	2011-02-02	1	-0/+1
*	unary <; countup two type parameters; --recursivePath should work now	Araq	2011-01-29	1	-2/+3
*	changes to threads; --recursivePath support	Araq	2011-01-29	1	-1/+3
*	basic thread support; still broken on Windows; untested on Mac OS X	Araq	2011-01-18	1	-0/+1
*	explicit indices in array literals	Araq	2011-01-16	1	-0/+2
*	Feature: explicit string representation for enum fields	Araq	2011-01-11	1	-0/+11
*	bugfix: floating point precision; added strutils.formatFloat	Araq	2011-01-09	1	-0/+3
*	additions to complex module	Araq	2011-01-07	1	-0/+1
*	implemented 'emit' pragma	Araq	2011-01-07	1	-1/+2
*	added test tmultim4.nim	Araq	2011-01-06	1	-0/+1
*	better tester; yet another iterator bugfix	Araq	2011-01-06	1	-0/+2
*	bugfix: multiple yield statements and loop body vars	Araq	2010-12-13	1	-1/+3
*	added strutils.align	Araq	2010-12-07	1	-0/+1
*	docgen understands and ignores when false	Araq	2010-11-18	1	-4/+5
*	pegs: captured search loop	Araq	2010-11-07	1	-0/+1
*	Bugfix: niminst: nimrod is not default dir for every project	Araq	2010-11-02	1	-0/+1
*	bugfix: dialogs.ChooseFilesToOpen	Araq	2010-11-01	1	-0/+2
*	added os.findExe	Araq	2010-10-31	1	-0/+1
*	pegs: bugfixes and extensions	Araq	2010-10-31	1	-1/+2
*	bugfixes: htmlparser module	Araq	2010-10-30	1	-0/+16
*	version 0.8.10	Araq	2010-10-21	1	-2/+5
*	proper parameter order for os.copyFile/os.moveFile	Araq	2010-09-21	1	-0/+1
*	bugfix: overflow checking for small ints; bugfix: tiny C works again	Araq	2010-09-20	1	-0/+1
*	fixes for exception handling; added system.compileOption	Araq	2010-09-13	1	-1/+3
*	c2nim: new features & bugfixes	Andreas Rumpf	2010-08-11	1	-0/+1
*	DLL generation of the stdlib for unix	Andreas Rumpf	2010-08-04	1	-0/+2
*	before stack init change	Andreas Rumpf	2010-08-01	1	-0/+4

=========================================== Questions and Answers =========================================== General ======= What is Nimrod? --------------- Nimrod is a new statically typed, imperative programming language, that supports procedural, functional, object oriented and generic programming styles while remaining simple and efficient. A special feature that Nimrod inherited from Lisp is that Nimrod's abstract syntax tree (*AST*) is part of the specification - this allows a powerful macro system which can be used to create domain specific languages. Nimrod does not sacrifice flexibility for speed. You get both. .. Don't give me that marketing crap. What is Nimrod? -------------------------------------------------- Nimrod = Mutable value based datatypes + static binding + sugar to make this programming modell as convenient as possible Why is it named Nimrod? ----------------------- You have to find out for yourself. If you don't find a tongue-in-cheek interpretation you will have to look harder. How is Nimrod licensed? ----------------------- The Nimrod compiler is GPL licensed, the runtime library is LGPL licensed. This means that you can use any license for your own programs developed with Nimrod. If I receive enough requests with good arguments, I may change the license of Nimrod to the BSD license. How stable is Nimrod? --------------------- The compiler is in development and some important features are still missing. However, the compiler is quite stable already: It is able to compile itself and a substantial body of other code. Until version 1.0.0 is released, incompatibilities with older versions of the compiler will be introduced. The semantic details of overloading, macros/templates/generics and iterators and their interactions are subject to change. How fast is Nimrod? ------------------- Benchmarks have not been ported yet and support for threads is missing. But in the worst case, you can get the same performance as in C if you decide to write as low-level Nimrod code as C requires you to do. That said the only overhead Nimrod has over C is the GC which has been tuned for years. What about JVM/CLR backends? ---------------------------- A JVM backend is almost impossible. The JVM is not expressive enough. It has never been designed as a general purpose VM anyway. A CLR backend is possible but would require much work. Compilation =========== Which option to use for the fastest executable? ----------------------------------------------- For the standard configuration file, ``-d:release`` does the trick. Which option to use for the smallest executable? ------------------------------------------------ For the standard configuration file, ``-d:quick --opt:size`` does the trick. Execution of GCC fails (Windows) -------------------------------- On Windows the configuration file ``config\nimrod.cfg`` assumes that GCC is in ``$nimrod\dist\mingw\bin``: This is where the Windows installer puts GCC. If you delete the line ``gcc.path = r"$nimrod\dist\mingw\bin"``, Nimrod uses the GCC from your ``PATH`` environment variable. If you cannot modify ``$nimrod\config\nimrod.cfg``, copy ``$nimrod\config\nimrod.cfg`` to ``%APPDATA%\nimrod.cfg`` and modify ``%APPDATA%\nimrod.cfg`` instead. To determine what ``%APPDATA%`` means for your Windows account, use the shell command:: echo %APPDATA% How do I use a different C compiler than the default one? --------------------------------------------------------- Edit the ``config/nimrod.cfg`` file. Change the value of the ``cc`` variable to one of the following: ============== ============================================ Abbreviation C/C++ Compiler ============== ============================================ ``dmc`` Digital Mars C++ ``wcc`` Watcom C++ (now unsupported!) ``bcc`` Borland C++ (now unsupported!) ``vcc`` Microsoft's Visual C++ ``gcc`` Gnu C ``pcc`` Pelles C (now unsupported!) ``lcc`` Lcc-win32 (now unsupported!) ``tcc`` Tiny C ``llvm_gcc`` LLVM-GCC compiler ``icc`` Intel C++ compiler ``ucc`` Generic UNIX C compiler ============== ============================================ If your C compiler is not in the above list, try using the *generic UNIX C compiler* (``ucc``). If the C compiler needs different command line arguments try the ``--passc`` and ``--passl`` switches. Unsupported compilers contain serious bugs that keep them from bootstrapping Nimrod.