Usually I've seen the * character used for convolution in written mathematics, which I'm sure Luis et al would approve of replacing this silly multiplication operator ;)
In mathematics, Knuth's up-arrow notation is a method of notation for very large integers, introduced by Donald Knuth in 1976. It is closely related to the Ackermann function and especially to the hyperoperation sequence. The idea is based on the fact that multiplication can be viewed as iterated addition and exponentiation as iterated multiplication. Continuing in this manner leads to iterated exponentiation (tetration) and to the remainder of the hyperoperation sequence, which is commonly denoted using Knuth arrow notation.
== Introduction ==
The ordinary arithmetical operations of addition,...
In mathematics, Knuth's up-arrow notation is a method of notation for very large integers, introduced by Donald Knuth in 1976. It is closely related to the Ackermann function and especially to the hyperoperation sequence. The idea is based on the fact that multiplication can be viewed as iterated addition and exponentiation as iterated multiplication. Continuing in this manner leads to iterated exponentiation (tetration) and to the remainder of the hyperoperation sequence, which is commonly denoted using Knuth arrow notation.
== Introduction ==
The ordinary arithmetical operations of addition,...
For xor they probably looked at ⊻ and went "Hmm, ^ is close enough, right?" "No, wouldn't everyone confuse that with AND?" "Well, do YOU have any better ideas?"
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
command="git clone github.com/cheddar-lang/Cheddar.git; cd Cheddar; eval npm install;echo 'alias cheddarrepl=\"node $DIR/Cheddar/dist/interpreter/tests/t_repl.js\"' >> ~/.bash_profile"
if [ -f ~/.bash_profile ];
then
if grep -q 'cheddarrepl' ~/.bash_profile
then
echo "Script already ran, or remove the any mentions of `cheddarrepl` from your .bash_profile."
else
if [ ! -d ~/Cheddar ];
then
eval $command
else
echo "Please delete the Cheddar directory before retrying."
I saw a line of C that looked like this:
!ErrorHasOccured() ??!??! HandleError();
It compiled correctly and seems to run ok. It seems like it's checking if an error has occurred, and if it has, it handles it. But I'm not really sure what it's actually doing or how it's doing it. It does look l...
i never uninstall anything and I have so many projects that I installed the dependancies and then the project didn't work out
@EᴀsᴛᴇʀʟʏIʀᴋ I can try windows with bash if you want
nvm I don't have npm installed
pi is still loading
sh: 1: grunt: not found
npm ERR! Linux 4.1.13-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.6
npm ERR! npm v2.11.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] postinstall: `grunt`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] postinstall script 'grunt'.
npm ERR! This is most likely a problem with the Cheddar package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
I did not have grunt
bbl I'll install grunt sometime for you @EᴀsᴛᴇʀʟʏIʀᴋ
What kinds of higher-order builtins can I implement to make recursion shorter? Right now I have to use the conditional operator and that gets really long really quickly. (Pretzel)
A laser shoots a straight beam in one of the four orthogonal directions, indicated by <>^v. Determine whether it will hit the target O on a rectangular grid.
Each of these will hit (True):
.....
...O.
.....
...^.
.....
>O.
...
v....
O....
...........
...........
O.........<
...........
T...