mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix Makefile and README.md for 2000/jarijyrki

Browse Source
This commit is contained in:
Landon Curt Noll committed 2023-03-15 12:32:32 -07:00
1 parent b5a791a7a9
commit f408bd1fd8
3 files changed
+588 -460
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2000/jarijyrki/.gitignore
+1
View File
@@ -1 +1,2 @@
jarijyrki jarijyrki
myedits.info
2000/jarijyrki/Makefile
+304 -186
View File
@@ -1,215 +1,333 @@
#!/bin/make #!/usr/bin/env make
# 2000 makefile
# #
# Copyright (C) Simon Cooper, Landon Curt Noll, Peter Seebach # IOCCC 2000 winning entry - jarijyrki
# and Leonid A. Broukhis, 2000.
# All Rights Reserved. Permission for personal, educational or non-profit
# use is granted provided this this copyright and notice are included in its
# entirety and remains unaltered. All other uses must receive prior permission
# from the contest judges.
SHELL= /bin/sh ################################################################################
CAT= cat
RM= rm
SED= sed
TRUE= true
#CINCLUDE= -I ${HOMEBREW_PREFIX}/include/SDL2
# optimization
# #
# Most compiles will safely use -O2. Some can use only -O. # Regarding individual entries:
# A few compilers have broken optimizers and thus you may #
# not want anything. # IOCCC winning entry code may not work on your system. Even with standards,
# conditions and build environments change, especially when it comes to more
# extreme code such you might find in an IOCCC winner. Moreover, what was
# allowed and liked in one IOCCC contest may no longer be liked/allowed in
# later IOCCC years.
#
# Corrections on winning author and fixing typos in remarks are VERY WELCOME.
#
# GitHub pull requests are welcome:
#
# If you have a patch that might make running an entry work in modern Unix-like
# environments, please create a GitHub pull request for the IOCCC judges to
# consider.
#
# Suggestions and corrections regarding Makefiles, winning author information,
# fixing typos in remarks, and code patches are welcome via opening a GitHub
# issue or better yet, by creating a GitHub pull request for the IOCCC judges
# to consider. To form a GitHub issue or GitHub pull, please visit:
#
# https://github.com/ioccc-src/winner
#
################################################################################
# This work by Landon Curt Noll and Leonid A. Broukhis is licensed under:
#
# Creative Commons Attribution-ShareAlike 3.0 Unported License.
#
# See: http://creativecommons.org/licenses/by-sa/3.0/
#############################
# shell used by this Makefile
#############################
#
SHELL= bash
#######################
# common tool locations
#######################
#
include ../../var.mk
# Set X11_LIBDIR to the directory where the X11 library resides
#
#X11_LIBDIR= /usr/X11R6/lib
#X11_LIBDIR= /usr/X11/lib
X11_LIBDIR= /opt/X11/lib
# Set X11_INCLUDEDIR to the directory where the X11 include files reside
#
#X11_INCDIR= /usr/X11R6/include
#X11_INCDIR= /usr/X11/include
X11_INCDIR= /opt/X11/include
# Common C compiler warnings to silence
#
#CSILENCE=
CSILENCE= -Wno-char-subscripts -Wno-empty-body -Wno-error \
-Wno-implicit-function-declaration -Wno-implicit-int
# Common C compiler warning flags
#
#CWARN= ${CSILENCE}
#CWARN= -Wall ${CSILENCE}
CWARN= -Wall -Wextra ${CSILENCE}
#CWARN= -Wall -Wextra -pedantic ${CSILENCE}
# Compiler standard
#
#CSTD=
#CSTD= -ansi
CSTD= -std=gnu99
# Compiler bit architecture
#
# Some entries require 32-bitness:
# ARCH= -m32
#
# Some entries require 64-bitness:
# ARCH= -m64
#
# By default we assume nothing:
#
ARCH=
# Defines that are needed to compile
#
#CDEFINE=
CDEFINE= -DNeedFunctionPrototypes \
-DU=40 -DT=98 '-Dz=(T+1)*U*U' -DQ=80 -DS=20 -DN=10 -DB=5 -DG=23 \
-Dp=7 '-DM=((p+1)*Q)+S' '-DH=(G*S)+S+S' -DC=XK_Up -DL=XK_Down \
-DO=XK_Left -DV=XK_Right -DR=XK_Escape -D_=XK_BackSpace
# Include files that are needed to compile
#
#CINCLUDE=
#CINCLUDE= -include stdlib.h
#CINCLUDE= -include stdio.h
#CINCLUDE= -include stdlib.h -include stdio.h
CINCLUDE= -I ${X11_INCDIR} -I ${X11_INCDIR}/X11
#CINCLUDE= `${SDL2_CONFIG} --cflags`
# Optimization
#
# Most compiles will safely use -O2. Some can use only -O1 or -O.
# A few compilers have broken optimizers or this entry make break
# under those buggy optimizers and thus you may not want anything.
# Reasonable compilers will allow for -O3.
# #
#OPT= #OPT=
#OPT= -O #OPT= -O
OPT= -O2 #OPT= -O1
#OPT= -O2
OPT= -O3
# flags for ANSI compiles # Default flags for ANSI C compilation
# #
# NOTE: Some ANSI compilers make use of -Xa to turn on ANSI mode, CFLAGS= ${CSTD} ${CWARN} ${ARCH} ${CDEFINE} ${CINCLUDE} ${OPT}
# others such as gcc may want -ansi, others (Compaq Tru64 Unix)
# want -std1, and others may want nothing at all.
# Adjust the CFLAGS line as needed.
#
# NOTE: Some compilers cannot optimize, or optimize some entries
# incorrectly. You might want to turn on -O to see if your
# compiler can handle them.
#
#
#CFLAGS= -Xa ${OPT}
#CFLAGS= -std1 $(OPT)
CFLAGS= -ansi ${OPT}
NO_ANSI_CFLAGS= # Libraries needed to build
#NO_ANSI_CFLAGS= #
#LIBS=
#LIBS= -lm
LIBS= -L ${X11_LIBDIR} -lX11
#LIBS= `${SDL2_CONFIG} --libs`
# NOTE: On some systems, the library path does not include the location # C compiler to use
# of the X11 libraries. You might need to use a -L/path/to/X11/lib/dir
# in order to compile with these libs.
#
X11CCFLAGS= -I/usr/X11R6/include -I/usr/X11R6/include/X11 -I/usr/include/X11
#X11CCFLAGS=
X11LDFLAGS= -L/usr/X11R6/lib
#X11LDFLAGS=
# Perl
#
PERL= perl
#PERL= perl5
# ANSI compiler
#
# Set CC to the name of your ANSI compiler.
#
# Some entries seem to need gcc. If you have gcc, set
# both CC and MAY_NEED_GCC to gcc.
#
# If you do not have gcc, set CC to the name of your ANSI compiler, and
# set MAY_NEED_GCC to either ${CC} (and hope for the best) or to just :
# to disable such programs.
# #
CC= cc CC= cc
MAY_NEED_GCC= gcc #CC=clang
#CC=gcc
# winners that compile under ANSI C # Compiler add-ons or replacements for clang only
# #
WINNERS= anderson schneiderwent primenum bellard bmeyer briddlebane dhyang \ ifeq ($(CC),clang)
dmy2jd jarijyrki dlowe natori rince robison thadgavin tomx
ALT_NAMES= schneiderwent.orig briddlebane.orig thadgavin.orig
DATA_FILES= schneiderwent_files bmeyer_files jarijyrki_files
all: ${WINNERS}
# Best use of flags
# #
anderson: anderson.c CSILENCE+= -Wno-float-conversion -Wno-float-equal -Wno-implicit-int-conversion \
${CC} ${CFLAGS} $? -o $@ -Wno-missing-prototypes -Wno-missing-variable-declarations -Wno-pedantic \
-Wno-poison-system-directories -Wno-shadow -Wno-shorten-64-to-32 \
# Most Timely Output -Wno-sign-conversion -Wno-strict-prototypes
# #
schneiderwent: schneiderwent.c CWARN+= -Weverything
${CC} ${CFLAGS} $? -o $@
schneiderwent_files: schneiderwent.data
schneiderwent.orig: schneiderwent.orig.c
${CC} ${CFLAGS} $? -o $@
# Best Abuse of CPP
# #
primenum: primenum.c endif
${CC} ${CFLAGS} $? -o $@
# Most Specific Output # Specific add-ons or replacements for gcc only
# #
bellard: bellard.c ifeq ($(CC),gcc)
${CC} ${CFLAGS} $? -o $@ #
#CSILENCE+=
#
#CWARN+=
#
endif
# Best Utility
#
# machines operating in 64 bit mode:
#
bmeyer: bmeyer.c
${CC} -DY= -O6 $? -o $@ -lm
#
# linux/x86, glibc 2.0, libc4/5:
#
# bmeyer: bmeyer.c
# ${CC} -DY="__setfpucw(0x127f)" -O6 $? -o $@ -lm
#
# linux/x86, glibc 2.1:
#
# bmeyer: bmeyer.c
# ${MAY_NEED_GCC} -DY='int x=0x127f; __asm__ ("fldcw %0" : : "m" (*&x))' \
# -O6 $? -o $@ -lm
bmeyer_files: lavabus.pgm lenna.glic michael.pgm ##############################
# Special flags for this entry
# Best Abuse of User ##############################
# #
briddlebane: briddlebane.c ENTRY= jarijyrki
${CC} ${CFLAGS} $? -o $@ -lm PROG= ${ENTRY}
briddlebane.orig: briddlebane.orig.c
${CC} ${CFLAGS} $? -o $@ -lm
# Best Layout
# #
dhyang: dhyang.c OBJ= ${PROG}.o
${CC} ${CFLAGS} $? -o $@ DATA= sheet1.info
TARGET= ${PROG}
dmy2jd: dmy2jd.c
${CC} ${CFLAGS} $? -o $@
# Best of Show
# #
jarijyrki: jarijyrki.c ALT_OBJ=
${CC} ${X11CCFLAGS} ${CFLAGS} -DNeedFunctionPrototypes \ ALT_TARGET=
-DU=40 -DT=98 '-Dz=(T+1)*U*U' -DQ=80 -DS=20 -DN=10 -DB=5 -DG=23 \
-Dp=7 '-DM=((p+1)*Q)+S' '-DH=(G*S)+S+S' -DC=XK_Up -DL=XK_Down \
-DO=XK_Left -DV=XK_Right -DR=XK_Escape -D_=XK_BackSpace \
$? -o $@ ${X11LDFLAGS} -lX11
jarijyrki_files: sheet1.info
# Worst Abuse of the Rules #################
# build the entry
#################
# #
# NOTE: You will need to adjust this path to the place where Perl has been all: data ${TARGET}
# installed on your system. Running "perl -V" may help you locate
# this place.
#
# The following bit of perl may help determining the values you need:
#
# perl -MConfig -e 'print "$Config{archlibexp}/CORE\n"'
#
#
dlowe: dlowe.c
${CC} ${NO_ANSI_CFLAGS} -DPERL_POLLUTE \
`${PERL} -MExtUtils::Embed -e ccopts` $? -o $@ \
`${PERL} -MExtUtils::Embed -e ldopts`
# Best Small Program
#
natori: natori.c
${CC} ${CFLAGS} $? -o $@ -lm
# Astronomically Obfuscated
#
rince: rince.c
${CC} ${X11CCFLAGS} ${CFLAGS} -DM_PI=3.14159265358979323846 \
$? -o $@ -lm ${X11LDFLAGS} -lX11
# Best game
#
robison: robison.c
${CC} ${CFLAGS} $? -o $@
# Most Portable Output
#
thadgavin: thadgavin.c
${CC} ${CFLAGS} $? -o $@ -lcurses -lm
thadgavin.orig: thadgavin.orig.c
${CC} ${CFLAGS} $? -o $@ -lncurses -lm
# Most Complete Program
#
tomx: tomx.c
${CC} ${CFLAGS} $? -o $@
everything: ${WINNERS} ${ALT_NAMES} ${DATA_FILES}
clean:
${RM} -f *.o a.out core ${WINNERS}
clobber: clean
${RM} -f ${WINNERS}
${RM} -f ${ALT_NAMES}
nuke: clobber
@${TRUE} @${TRUE}
install: all .PHONY: all alt data everything clean clobber install \
${CAT} ${WINNERS} ${ALT_NAMES} > /dev/null love haste waste maker easter_egg sandwich \
supernova deep_magic magic charon pluto
${PROG}: ${PROG}.c
${CC} ${CFLAGS} $< -o $@ ${LIBS}
# alternative executable
#
alt: data ${ALT_TARGET}
@${TRUE}
# data files
#
data: ${DATA}
@${TRUE}
# both all and alt
#
everything: all alt
###############
# utility rules
###############
#
clean:
${RM} -f ${OBJ} ${ALT_OBJ}
@-if [ -f indent.c ]; then \
echo ${RM} -f indent.c; \
${RM} -f indent.c; \
fi
clobber: clean
${RM} -f ${TARGET} ${ALT_TARGET}
${RM} -f myedits.info
@-if [ -e sandwich ]; then \
${RM} -f sandwich; \
echo 'ate sandwich'; \
fi
install:
@echo "Dr. Spock says that is not logical!"
@${TRUE}
# you may be able to misunderstand the source by reading indent.c
#
indent.c: ${PROG}.c
@if which "${GINDENT}" >/dev/null 2>&1; then \
echo ${RM} -f $@; \
${RM} -f $@; \
echo "${GINDENT} < $< > $@"; \
${GINDENT} < $< > $@; \
elif which "${INDENT}" >/dev/null 2>&1; then \
echo ${RM} -f $@; \
${RM} -f $@; \
echo "${INDENT} < $< > $@"; \
${INDENT} < $< > $@; \
else \
echo "no intent tool found, ident $< yourself, sorry"; \
echo "exit 1"; \
exit 1; \
fi
##################
# 133t hacker rulz
##################
#
love:
@echo 'not war?'
@${TRUE}
haste:
$(MAKE) waste
@${TRUE}
waste:
@echo 'haste'
@${TRUE}
maker:
@echo 'Participate in a maker faire'
@${TRUE}
easter_egg:
@echo "you expected to often misunderstand this $${RANDOM} magic"
@echo "chongo '<was here>' /\\oo/\\"
@echo "Eggy"
sandwich: easter_egg
@if [ `id -u` -eq 0 ]; then \
echo 'Okay.'; \
echo "$${RANDOM}`date +%s`$${RANDOM}" > $@; \
else \
echo 'What? Make it yourself.'; \
exit 1; \
fi
# Understand the history of the Homebrew Computer Club
# as well as the West Coast Computer Faire and
# you might be confused different. :-)
#
supernova: sandwich
@-if [ -r .code_anal ]; then \
${RM} -f .code_anal_v6; \
else \
echo "planet deniers, like some members of the IAU, are so cute when they try to defend their logic"; \
fi
@echo "A $@ helps ${MAKE} the elements that help form planets"
@${TRUE}
deep_magic: supernova
@-if [ -r .code_anal ]; then \
ccode_analysis --deep_magic 7889066cdbdf09b0408021754586e895be641cc9be29e7eafd3ca65359541f17 \
--FNV1a_hash_512_bit -v2 "${PROG}" "${PROG}.c"; \
else \
echo "Wrong! Do it again!"; \
sleep 2; \
echo "Wrong! Do it again!"; \
sleep 2; \
echo "Wrong! Do it again!"; \
fi
@${TRUE}
magic: deep_magic
@-if [ -r .code_anal ]; then \
ccode_analysis --level 20003 --mode 5717175 --FNV1a_hash_512_bit -v2 "${PROG}" "${PROG}.c"; \
else \
echo "If you don't eat yer meat, you can't have any pudding!"; \
echo "How can you have any pudding if you don't eat yer meat?!"; \
fi
@${TRUE}
# The IOCCC resident astronomer states
#
charon: magic
@echo "$@ is a dwarf planet"
@echo "dwarf is a type of planet"
@echo "therefore IAU, $@ is a planet"
pluto: charon
${MAKE} charon
@echo "$@ is a dwarf planet"
@echo "dwarf is a type of planet"
@echo "therefore, $@ is a planet"
@echo "having lots of planets is good feature because supernovae can help ${MAKE} a lot of them"
2000/jarijyrki/README.md
+283 -274
View File
@@ -1,373 +1,382 @@
Best of Show: # Best of Show:
Jari Arkko Jari Arkko
Kauppalantie 25A7, Kauppalantie 25A7,
02700 Kauniainen, 02700 Kauniainen,
Finland Finland
http://www.arkko.com http://www.arkko.com
Jyrki Holopainen Jyrki Holopainen
Forsellesintie 1-3A10, Forsellesintie 1-3A10,
02700 Kauniainen, 02700 Kauniainen,
Finland Finland
http://personal.eunet.fi/pp/halo/ http://personal.eunet.fi/pp/halo/
# To build:
Judges' Comments: ```sh
make
```
You will need X11 header files and libraries installed to build this program.
To build: (You will need X11 header files and libraries installed to ### To run:
build this program)
make jarijyrki ```sh
./jarijyrki < infile.info > outfile.info
```
To run: (You will need a system capable of displaying the results of You will need a system capable of displaying the results of X Window programs.
X Window programs)
./jarijyrki < sheet1.info > myedits.info ### Try:
This entry is one of those that makes you wonder why some commercial ```sh
software needs tens to hundreds of megabytes to install! This entry ./jarijyrki < sheet1.info > myedits.info
does not simply do the basics, it includes graphing features. All this ```
program needs now is a flight simulator!
## Judges' comments:
This entry is one of those that makes you wonder why some commercial
software needs tens to hundreds of megabytes to install! This entry
does not simply do the basics, it includes graphing features. All this
program needs now is a flight simulator!
## Author's comments:
1. OVERVIEW
This program is an X-Windows based spreadsheet program.
The main functions it supports are:
* Text cells
* Numeric cells
* Arithmetic operations: + - * /
* Pie charts
* Histograms
* Cell editing
* Formula line
* Dynamic recalculation
* Error detection
* Recursion detection
* Movement within the spreadsheet with cursor keys
* Movement within the spreadsheet with mouse
* Scrolling
* Loading and saving spreadsheets
* Visual style configuration
Selected Author's Comments: 2. USAGE INSTRUCTIONS
1. OVERVIEW 2.1. Quick Guide
This program is an X-Windows based spreadsheet program. Starting: ./jarijyrki < sheet1.info > myedits.info
The main functions it supports are: Stopping: Esc
Movement: Click mouse or cursor keys
Editing: Currently selected cell is always in edit state.
Press any key to add a character at the end of the
formula; press BackSpace to delete the last one.
Formulas: 123.45
A1 A2 +
B1 B2 -
C1 C2 *
D1 D2 /
Pie charts: A1 A2 A3 ... An @
Histograms: A1 A2 A3 ... An !
* Text cells 2.2. Starting and Loading Spreadsheets
* Numeric cells
* Arithmetic operations: + - * /
* Pie charts
* Histograms
* Cell editing
* Formula line
* Dynamic recalculation
* Error detection
* Recursion detection
* Movement within the spreadsheet with cursor keys
* Movement within the spreadsheet with mouse
* Scrolling
* Loading and saving spreadsheets
* Visual style configuration
2. USAGE INSTRUCTIONS To start the spreadsheet program with an existing
spreadsheet, use the following command line:
2.1. Quick Guide ./jarijyrki < sheet1.info
Starting: ./jarijyrki < sheet1.info > myedits.info The file sheet1.info has been provided as an example.
Stopping: Esc This file contains a set of financial numbers and two
Movement: Click mouse or cursor keys graphical entities - a pie chart and a histogram - based
Editing: Currently selected cell is always in edit state. on them. We recommend starting the use of the program
Press any key to add a character at the end of the from this file, as a way to study and learn the formula
formula; press BackSpace to delete the last one. language supported by the program.
Formulas: 123.45
A1 A2 +
B1 B2 -
C1 C2 *
D1 D2 /
Pie charts: A1 A2 A3 ... An @
Histograms: A1 A2 A3 ... An !
2.2. Starting and Loading Spreadsheets To start the program with an empty sheet, use
To start the spreadsheet program with an existing ./jarijyrki < /dev/null
spreadsheet, use the following command line:
./jarijyrki < sheet1.info [Alternatively, /dev/zero could be used but that may not exist
on all systems.]
The file sheet1.info has been provided as an example. 2.3. Exiting and Saving Spreadsheets
This file contains a set of financial numbers and two
graphical entities - a pie chart and a histogram - based
on them. We recommend starting the use of the program
from this file, as a way to study and learn the formula
language supported by the program.
To start the program with an empty sheet, use Normally the user obviously wants to edit the spreadsheet.
After the spreadsheet program finishes, it outputs the
edited spreadsheet to the standard output. Hence, when
the spreadsheet window has come up, you've made your changes,
and you press the Esc key the program finishes. To save
the results in a file, the following typical command line
would be used:
./jarijyrki < /dev/null ./jarijyrki < sheet1.info > myedits.info
[Alternatively, /dev/zero could be used but that may not exist 2.4. Visual Overview
on all systems.]
2.3. Exiting and Saving Spreadsheets On top of the window the Formula Area shows the formula (or text)
of the currently selected cell. The program starts with A1 as
being the current cell. Below the Formula Area is the Column
Letters Area: A, B, and so on. Correspondingly, on the left
side of the window is the Row Numbers Area: 1, 2, and so on.
The rest of the window is dedicated to the actual spreadsheet
cells.
Normally the user obviously wants to edit the spreadsheet. The example spreadsheet, sheet1.info, provided with this
After the spreadsheet program finishes, it outputs the program contains two sets of numbers in the visible area
edited spreadsheet to the standard output. Hence, when of the spreadsheet. The top set of numbers forms the
the spreadsheet window has come up, you've made your changes, product-by-product turnover breakdown of an imaginary
and you press the Esc key the program finishes. To save company. Below it is the yearly development of the
the results in a file, the following typical command line company profits. On the top right corner is a pie chart
would be used: showing the turnover breakdown in graphical form, and
on the bottom right corner is a histogram showing the
yearly development. If you scroll the window you can
see additional data from the spreadsheet.
./jarijyrki < sheet1.info > myedits.info 2.5. Movement and Scrolling
Use cursor keys to move left, right, up, and down among the cells.
[Note that it is not possible to move around the formula; the
formula can only be edited from its end by adding or removing
characters.] You may also click the mouse on a cell to cause it
to be activated as the current one.
Going beyond the borders of the window results in scrolling
the current view. It is not possible to go up from first row
or left from the first column; but it is possible to wrap back
to start from the last row and last column.
2.6. Formula
The spreadsheet formulas operate on a stack. Operands of an
operation (e.g. plus) are first pushed to the stack and then
the operation is performed. If a formula on a cell produces
*exactly* one result then that is shown in the cell. Otherwise,
the formula is interpreted as a string and shown as it is.
2.4. Visual Overview An example of a simple formula, simply specifying a number
is
On top of the window the Formula Area shows the formula (or text) 123.50
of the currently selected cell. The program starts with A1 as
being the current cell. Below the Formula Area is the Column
Letters Area: A, B, and so on. Correspondingly, on the left
side of the window is the Row Numbers Area: 1, 2, and so on.
The rest of the window is dedicated to the actual spreadsheet
cells.
The example spreadsheet, sheet1.info, provided with this Another simple formula refers to a cell:
program contains two sets of numbers in the visible area
of the spreadsheet. The top set of numbers forms the
product-by-product turnover breakdown of an imaginary
company. Below it is the yearly development of the
company profits. On the top right corner is a pie chart
showing the turnover breakdown in graphical form, and
on the bottom right corner is a histogram showing the
yearly development. If you scroll the window you can
see additional data from the spreadsheet.
2.5. Movement and Scrolling A1
Use cursor keys to move left, right, up, and down among the cells. This particular example formula referred to the first cell of
[Note that it is not possible to move around the formula; the the first row in the spreadsheet. Arithmetic operations require
formula can only be edited from its end by adding or removing both arguments:
characters.] You may also click the mouse on a cell to cause it
to be activated as the current one.
Going beyond the borders of the window results in scrolling
the current view. It is not possible to go up from first row
or left from the first column; but it is possible to wrap back
to start from the last row and last column.
2.6. Formula
The spreadsheet formulas operate on a stack. Operands of an
operation (e.g. plus) are first pushed to the stack and then
the operation is performed. If a formula on a cell produces
*exactly* one result then that is shown in the cell. Otherwise,
the formula is interpreted as a string and shown as it is.
An example of a simple formula, simply specifying a number A1 A2 +
is B1 B2 *
C1 C2 -
D1 D2 /
123.50 More complex formulae can be constructed by combining these
simple ones:
Another simple formula refers to a cell: A1 A2 + 2 *
A1 This example calculated the sum of the cells A1 and A2, and then
multiplied the result by two.
This particular example formula referred to the first cell of The currently selected cell is always in a state where it can
the first row in the spreadsheet. Arithmetic operations require be edited. Press any key to add a character at the end of the
both arguments: formula; press BackSpace to delete the last one. Any resulting
recalculations are immediately visible. [Note how much nicer
this feature is as you get used to it, compared to the behaviour
of certain commercial spreadsheet programs.]
A1 A2 + 2.7. Graphical Formulas
B1 B2 *
C1 C2 -
D1 D2 /
More complex formulae can be constructed by combining these The program supports two types of graphical representations of the
simple ones: data in the cells: pie charts and histograms. The pie chart can
consist of any number of slices, and is constructed by putting
the pie amounts in stack and using the @ operator. The program
automatically computes the relative size of the slices.
A1 A2 + 2 * A1 A2 A3 A4 @
This example calculated the sum of the cells A1 and A2, and then This example would draw a pie slice of four cells, A1 to A4.
multiplied the result by two. The pie formula is shown above the pie for reference.
The currently selected cell is always in a state where it can The histograms are drawn in a similar manner, by using the !
be edited. Press any key to add a character at the end of the operator:
formula; press BackSpace to delete the last one. Any resulting
recalculations are immediately visible. [Note how much nicer
this feature is as you get used to it, compared to the behaviour
of certain commercial spreadsheet programs.]
2.7. Graphical Formulas A1 A2 A3 A3 !
The program supports two types of graphical representations of the 2.8. Errors in Formulas
data in the cells: pie charts and histograms. The pie chart can
consist of any number of slices, and is constructed by putting
the pie amounts in stack and using the @ operator. The program
automatically computes the relative size of the slices.
A1 A2 A3 A4 @ The program detects recursive reference attempts, references
cells not containing a numerical value, attempts to define
formulas with zero, two, or more results remaining in the stack,
and syntax errors of formulas. Note that typically as the user
types in a formula, it toggles between valid and invalid forms
dynamically as all single character changes are immediately
taken in account. This is not dangerous, just complete the
formula and view the results.
This example would draw a pie slice of four cells, A1 to A4. Errors are signalled by showing the formula on a cell instead
The pie formula is shown above the pie for reference. of the numerical value supposedly returned by it.
The histograms are drawn in a similar manner, by using the ! Division by zero results in an IEEE Inf number.
operator:
A1 A2 A3 A3 ! 2.9. Compilation Parameters and Configuration
2.8. Errors in Formulas This section explains the meaning and rationale for the
compile time parameters:
The program detects recursive reference attempts, references -DC=XK_Up
cells not containing a numerical value, attempts to define -DL=XK_Down
formulas with zero, two, or more results remaining in the stack, -DO=XK_Left
and syntax errors of formulas. Note that typically as the user -DV=XK_Right
types in a formula, it toggles between valid and invalid forms -DR=XK_Escape
dynamically as all single character changes are immediately -D_=XK_BackSpace
taken in account. This is not dangerous, just complete the
formula and view the results.
Errors are signalled by showing the formula on a cell instead These definitions can be used to change the user interface
of the numerical value supposedly returned by it. of the program with respect to special keys. The four first
ones define the movement operations and the latter two ones
define the program termination and character deletion keys.
Typical modifications to these parameters include changing
character deletion to the key the user is most familiar with,
which could also be XK_Delete. XK_Escape might be better
in some cases as one of the function keys. Likewise for the
cursor keys.
Division by zero results in an IEEE Inf number.
2.9. Compilation Parameters and Configuration -DU=40
This section explains the meaning and rationale for the This parameter defines the maximum dimensions of the stored
compile time parameters: and handled spreadsheet (but see section 4.4 for a warning
about changing this without thinking about the consequences!).
-DC=XK_Up
-DL=XK_Down
-DO=XK_Left
-DV=XK_Right
-DR=XK_Escape
-D_=XK_BackSpace
These definitions can be used to change the user interface -DT=98
of the program with respect to special keys. The four first
ones define the movement operations and the latter two ones
define the program termination and character deletion keys.
Typical modifications to these parameters include changing
character deletion to the key the user is most familiar with,
which could also be XK_Delete. XK_Escape might be better
in some cases as one of the function keys. Likewise for the
cursor keys.
This parameter defines the maximum length of a formula in one
cell. Note the warning in 4.4.
-DU=40
This parameter defines the maximum dimensions of the stored -Dz="(T+1)*U*U"
and handled spreadsheet (but see section 4.4 for a warning
about changing this without thinking about the consequences!).
Defines the number of bytes in a spreadsheet file. The number is
automatically adjusted when the spreadsheet size parameters are
changed. Note the warning in 4.4.
-DT=98
This parameter defines the maximum length of a formula in one -DQ=80
cell. Note the warning in 4.4. -DS=20
These two parameters define the visual dimensions of a cell.
Changing these may be necessary on your system if the default
font sizes differ from those in the systems we've tested the
program with. S also defines the size of the left (x1) and top
margins (x2).
-Dz="(T+1)*U*U"
Defines the number of bytes in a spreadsheet file. The number is -DN=10
automatically adjusted when the spreadsheet size parameters are
changed. Note the warning in 4.4.
This is the x-indentation of text inside a cell. Changing
this may be necessary to suit other font sizes and
different X environments.
-DQ=80
-DS=20
These two parameters define the visual dimensions of a cell. -DB=5
Changing these may be necessary on your system if the default
font sizes differ from those in the systems we've tested the
program with. S also defines the size of the left (x1) and top
margins (x2).
This is the y-indentation of text inside a cell. Changing
this may be necessary to suit other font sizes and
different X environments.
-DN=10
This is the x-indentation of text inside a cell. Changing -DG=23
this may be necessary to suit other font sizes and
different X environments.
This parameter is the number of cell rows visible at one
time.
-DB=5
This is the y-indentation of text inside a cell. Changing -Dp=7
this may be necessary to suit other font sizes and
different X environments.
This parameter is one smaller than the number of cells columns
visible at one time.
-DG=23
This parameter is the number of cell rows visible at one -DM="((p+1)*Q)+S"
time. -DH="(G*S)+S+S"
These parameters are the window x and y sizes of the spreadsheet
program window. With these definitions, they are automatically
reflecting the at-one-time-visible cell row/column amounts.
Hence, we recommend changing the G and p parameters if you want
to change the window size in normal cases. Experimentation with
M and H can be used to get other types of effect such as adding
a margin also at the bottom of the window.
-Dp=7 3. IMPLEMENTATION
This parameter is one smaller than the number of cells columns It's better to just read the code. But note the use of
visible at one time. stack in the implementation of @ and ! operators, and note
the use of *#i in one of the macros [can you see why?].
Extreme compression has been the key in writing this
program. With compression have come the use of ASCII code
numbers instead of character constants and so on. [This
particular obfuscation is not really a desirable one as
it is not completely portable. But it certainly was a
necessary one.]
What does or does not "i(=)" do and why?
-DM="((p+1)*Q)+S" 4. WARNINGS AND CAVEATS
-DH="(G*S)+S+S"
These parameters are the window x and y sizes of the spreadsheet 4.1. X11 Paths in Compilation
program window. With these definitions, they are automatically
reflecting the at-one-time-visible cell row/column amounts.
Hence, we recommend changing the G and p parameters if you want
to change the window size in normal cases. Experimentation with
M and H can be used to get other types of effect such as adding
a margin also at the bottom of the window.
3. IMPLEMENTATION The given build file may have to be edited to insert correct
library and include file path names.
It's better to just read the code. But note the use of 4.2. Font Sizes
stack in the implementation of @ and ! operators, and note
the use of *#i in one of the macros [can you see why?].
Extreme compression has been the key in writing this
program. With compression have come the use of ASCII code
numbers instead of character constants and so on. [This
particular obfuscation is not really a desirable one as
it is not completely portable. But it certainly was a
necessary one.]
What does or does not "i(=)" do and why? We've tested the program with limited amount of X servers.
It is possible that other systems use default font sizes or
other parameters that cause the visual looks to be different
or perhaps even unusable; if this happens, changing compile-time
parameters explained in section 2.8 may help.
4. WARNINGS AND CAVEATS 4.3. Screen Sizes
4.1. X11 Paths in Compilation The size of the window as it comes up - a parameter as defined
in compile-time - has been set suitable for a small laptop screen.
Larger screens may benefit from setting these parameters higher.
Smaller screens require changing the parameters so that all of the
window becomes visible.
The given build file may have to be edited to insert correct 4.4. Spreadsheet Dimension Changes
library and include file path names.
4.2. Font Sizes The size of the read, manipulated, and stored spreadsheets is
defined by a compile time parameter. However, changing this
parameter is not entirely trivial. The following constraints
apply:
We've tested the program with limited amount of X servers. (a) Horizontal (alphabet) dimension handling will always be
It is possible that other systems use default font sizes or A to Z regardless of the actual allocated memory area.
other parameters that cause the visual looks to be different
or perhaps even unusable; if this happens, changing compile-time
parameters explained in section 2.8 may help.
4.3. Screen Sizes (b) Any change in the dimension parameter renders existing
spreadsheet files unsuitable.
The size of the window as it comes up - a parameter as defined 4.5. ASCII Reliance
in compile-time - has been set suitable for a small laptop screen.
Larger screens may benefit from setting these parameters higher.
Smaller screens require changing the parameters so that all of the
window becomes visible.
4.4. Spreadsheet Dimension Changes The software relies on running on ASCII-based code system.
Why? Because "32" is shorter than "' '".
The size of the read, manipulated, and stored spreadsheets is 4.6. Command Line Single Character Defines
defined by a compile time parameter. However, changing this
parameter is not entirely trivial. The following constraints
apply:
(a) Horizontal (alphabet) dimension handling will always be The use of single character (e.g. G or p) for a -D option
A to Z regardless of the actual allocated memory area. may break certain systems, if those characters are used
in the included X header files in certain kinds of places.
(b) Any change in the dimension parameter renders existing If this happens, you may move the offending character to
spreadsheet files unsuitable. a new name by exchanging it on the command line and in
the program with another character. Note that there are
4.5. ASCII Reliance *no* free characters in the program currently.
The software relies on running on ASCII-based code system.
Why? Because "32" is shorter than "' '".
4.6. Command Line Single Character Defines
The use of single character (e.g. G or p) for a -D option
may break certain systems, if those characters are used
in the included X header files in certain kinds of places.
If this happens, you may move the offending character to
a new name by exchanging it on the command line and in
the program with another character. Note that there are
*no* free characters in the program currently.