The rules of this game are very simple; ``one up'' the previous guy. You may only adjust one (1) thing about the previous persons program. For example, if you see a spelling error you may only change that in your next post. The second rule is that your ``one up'ed'' code MUST work. And the third and final rule is that you need to give a reason why your code is ``one up'ed'' from the previous. Beyond that, the sky's the limit. You may mutate the process and procedures to suit your needs. You may gang up in teams and try and get the program to mutate into something your team wants but the ``one up'', the ``working'' and the ``why'' rules must hold true. (If you are trying to mutate the procedure you either need to find a slick way of doing it, or make up a good enough reason not to cause a stink--No ``cause I wanted to'' allowed-.)
I will start off with a very simple program that has plenty potential to grow.
You may hold general discussions in this thread with your teammates if you feel like it--no private messages for recruiting you must hold all discussions here in the open.
Official ``one up'' code must be prefixed with the tags:
One up and Why:
...So without further adieu:
One up and Why:
Initial code.
(defun MyLine ( / cntr pt1 pt2 )
;;
;; History:
;; 08.22.06 -- Se7en
;;
(setq cntr 1
pt1
(getpoint
(strcat
"\nEnter point number "
(rtos cntr 2 0)
" please: "
)
)
)
(if pt1
(progn
(setq cntr (1+ cntr))
(setq pt2 (getpoint pt1
(strcat
"\nEnter point number "
(rtos cntr 2 0)
" please: "
)
)
)
)
(progn
(princ "\nYou have not entered a valid point; existing now.")
(quit)
)
)
(if pt2
(command "_.line" pt1 pt2 "")
(progn
(princ "\nYou have not entered a valid point")
(quit)
)
)
)
