lcpp
/
lci
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

minor formatting changes; adding unit tests to Travis CI

This commit is contained in:
Justin Meza 2015-03-08 17:22:36 -04:00
parent b56bedf908
commit 7046b90174
3 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.travis.yml
View File

@ -3,4 +3,4 @@ compiler:
- gcc - gcc
- clang - clang
# Change this to your needs # Change this to your needs
script: cmake . && make script: cmake . && make && ctest

22
README
View File

@ -17,21 +17,23 @@ LICENSE
You should have received a copy of the GNU General Public License You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>. along with this program. If not, see <http://www.gnu.org/licenses/>.
ABOUT ABOUT
lci is a LOLCODE interpreter written in C and is designed to be correct, lci is a LOLCODE interpreter written in C and is designed to be correct,
portable, fast, and precisely documented. portable, fast, and precisely documented.
- correct: Every effort has been made to test lci's conformance to the - Correct: Every effort has been made to test lci's conformance to the LOLCODE
LOLCODE language specification. Unit tests come packaged with the lci language specification. Unit tests come packaged with the lci source code.
source code.
- portable: lci follows the widely ported ANSI C specification allowing it - Portable: lci follows the widely ported ANSI C specification allowing it to
to compile on a broad range of systems. compile on a broad range of systems.
- fast: Much effort has gone into producing simple and efficient code
whenever possible to the extent that the above points are not - Fast: Much effort has gone into producing simple and efficient code whenever
compromized. possible to the extent that the above points are not compromized.
- precisely documented: lci uses Doxygen to generate literate code
documentation, browsable here. - Precisely documented: lci uses Doxygen to generate literate code
documentation, browsable here.
This project's homepage is at http://lolcode.org. For help, visit This project's homepage is at http://lolcode.org. For help, visit
http://groups.google.com/group/lci-general. To report a bug, go to http://groups.google.com/group/lci-general. To report a bug, go to

14
README.md
View File

@ -1,18 +1,20 @@
# lci # lci
![Build status](https://travis-ci.org/justinmeza/lci.svg?branch=future)
lci is a LOLCODE (http://lolcode.org) interpreter written in C and is designed lci is a LOLCODE (http://lolcode.org) interpreter written in C and is designed
to be correct, portable, fast, and precisely documented. to be correct, portable, fast, and precisely documented.
- correct: Every effort has been made to test lci's conformance to the LOLCODE - Correct: Every effort has been made to test lci's conformance to the LOLCODE
language specification. Unit tests come packaged with the lci source code. language specification. Unit tests come packaged with the lci source code.
- portable: lci follows the widely ported ANSI C specification allowing it to - Portable: lci follows the widely ported ANSI C specification allowing it to
compile on a broad range of systems. compile on a broad range of systems.
- fast: Much effort has gone into producing simple and efficient code whenever - Fast: Much effort has gone into producing simple and efficient code whenever
possible to the extent that the above points are not compromized. possible to the extent that the above points are not compromized.
- precisely documented: lci uses Doxygen to generate literate code - Precisely documented: lci uses Doxygen to generate literate code
documentation, browsable here. documentation, browsable here.
This project's homepage is at http://lolcode.org. For help, visit This project's homepage is at http://lolcode.org. For help, visit
@ -88,7 +90,3 @@ PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with You should have received a copy of the GNU General Public License along with
this program. If not, see <http://www.gnu.org/licenses/>. this program. If not, see <http://www.gnu.org/licenses/>.
### Prerequisites