start new:
tmux
start new with session name:
tmux new -s myname
This benchmark has been misleading for a while. It was originally made to demonstrate how JIT compilers can do all sorts of crazy stuff to your code - especially LuaJIT - and was meant to be a starting point of discussion about what exactly LuaJIT does and how.
As a result, its not indicative of what its performance may be on more realistic data. Differences can be expected because
/* use gettimeofday() to calculate the execution time in microseconds */ | |
#include <sys/time.h> | |
long timecost(void (*dosomething)()) | |
{ | |
struct timeval start, end; | |
long cost; | |
gettimeofday(&start, NULL); | |
dosomething(); | |
gettimeofday(&end, NULL); |
# compile | |
$ g++ zlib-example.cpp -lz -o zlib-example | |
# run | |
$ ./zlib-example | |
Uncompressed size is: 36 | |
Uncompressed string is: Hello Hello Hello Hello Hello Hello! | |
---------- |
/*! normalize.css v2.1.3 | MIT License | git.io/normalize */ | |
/* ========================================================================== | |
HTML5 display definitions | |
========================================================================== */ | |
/** | |
* Correct `block` display not defined in IE 8/9. | |
*/ |
/* Code: */ | |
#include <libxml/parser.h> | |
#include <libxml/xpath.h> | |
#include <stdio.h> | |
xmlDocPtr | |
getdoc (char *docname) | |
{ | |
xmlDocPtr doc; | |
doc = xmlParseFile(docname); |
Suppose that you are a programmer primarily working with compiled languages. Somehow you’ve got tired of those languages, there may be multiple valid reasons, and heard of a trendy new programming language called Rust. Looking at some webpages and the official forum, it looks great and you decides to try it out. It seems that Rust was a bit cumbersome to install in the past, but thanks to rustup the problem seems gone by now. Cargo seems to be great, so you follow the first sections of the Book and put a small greeting to the new language:
fn main() {
println!("Hello, world!");
}
Amazingly cargo run
runs without a hassle. It is kind of a miracle as you used to configure the build script, Makefile, projects or whatever before building things. Impressed, you realize that the executable is available in target/debug/hello
. You instinctively type ls -al
out (or is it dir
?) and
# As per this guide -- http://raspberrypi.stackexchange.com/questions/3617/how-to-install-unrar-nonfree#3618 | |
# Uninstall unrar-free. | |
sudo apt-get remove unrar-free | |
# Make sure you have a source repository by editing /etc/apt/sources.list. | |
cat /etc/apt/sources.list | |
# Sync the apt database. | |
sudo apt-get update |