#!/bin/bash
clear

OCCT=/usr/local/opencascade-7.1.0/bin/lin64/gcc/lib ;;; такого пути просто не существует, поэтому не знаю как быть, нужна ваша помощь 


CADREADER=/usr/local/cgxCadTools/CadReader/src/ ;;; здесь нет проблем


export LD_LIBRARY_PATH=$OCCT:$LD_LIBRARY_PATH
export CADREADER

exec $CADREADER/tmain $@

#lang racket
(define sum-of-first
  (lambda (n)
    (if (= n 1)
        1
        (+ (sum-of-first (- n 1))
           n))))

например, ввожу, в debugger
(sum-of-first 4)
работает только эта часть
(sum-of-first (- n 1))
полученный результат складывается в stack, в данном случае это
4
3
2
1 и вот здесь я поплыл т.к. в этом месте
(if (= n 1)
        1
код должен вылететь, а он нет, он начинает отрабатывать сумму
(+ (sum-of-first (- n 1))
           n)

#lang racket
(require racket/class
         racket/gui/base)
(define f (new frame% [label "My Art"]
                      [width 300]
                      [height 300]
                      [alignment '(center center)]))

(define (add-drawing p)
  (let ([drawer (make-pict-drawer p)])
;;make-pict-drawer: unbound identifier in module in: make-pict-drawer
    (new canvas% [parent f]
                 [style '(border)]
                 [paint-callback (lambda (self dc)
                                   (drawer dc 0 0))])))

<?xml version="1.0" encoding="UTF-8"?>
<!-- You may freely edit this file. See commented blocks below for -->
<!-- some examples of how to customize the build. -->
<!-- (If you delete it and reopen the project it will be recreated.) -->
<!-- By default, only the Clean and Build commands use this build script. -->
<!-- Commands such as Run, Debug, and Test only use this build script if -->
<!-- the Compile on Save feature is turned off for the project. -->
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
<!-- in the project's Project Properties dialog box.-->
<project name="jTessBoxEditor" default="default" basedir=".">
    <description>Builds, tests, and runs the project jTessBoxEditor.</description>
    <import file="nbproject/build-impl.xml"/>
    <property name="version" value="1.3"/>

     <target name="-post-compile">
        <copy todir="${build.classes.dir}">
            <fileset dir="." includes="readme*.html"/>
        </copy>
    </target>
    <target name="-post-jar">
        <move todir="./">
            <fileset dir="${dist.dir}" includes="${ant.project.name}.jar" />
        </move>
        <delete dir="${dist.dir}/lib"/>
    </target>
    <target name="-post-clean">
        <delete file="${ant.project.name}.jar"/>
    </target>
    <target name="dist" depends="clean,jar"
            description="create binary and source distribution archives">
        <mkdir dir="${dist.dir}"/>
        <zip zipfile="${dist.dir}/${ant.project.name}-${version}-src.zip">
            <zipfileset dir="." prefix="${ant.project.name}">
                <exclude name="**/.*"/>
                <exclude name="${dist.dir}/**"/>
                <exclude name="${build.dir}/**"/>
                <exclude name="doc/**"/>
                <exclude name="${ant.project.name}.jar"/>
            </zipfileset>
        </zip>
        <zip zipfile="${dist.dir}/${ant.project.name}-${version}.zip">
            <zipfileset dir="." includes="*,lib/**,data/**,tools/**,samples/**,tesseract-ocr/**" prefix="${ant.project.name}"
                        excludes="build.xml,src,build,dist,doc,nbproject">
                <exclude name="*.mf"/>
            </zipfileset>
        </zip>
        <delete dir="${dist.dir}/lib"/>
    </target>
    <!--

    There exist several targets which are by default empty and which can be
    used for execution of your tasks. These targets are usually executed
    before and after some main targets. They are:

      -pre-init:                 called before initialization of project properties
      -post-init:                called after initialization of project properties
      -pre-compile:              called before javac compilation
      -post-compile:             called after javac compilation
      -pre-compile-single:       called before javac compilation of single file
      -post-compile-single:      called after javac compilation of single file
      -pre-compile-test:         called before javac compilation of JUnit tests
      -post-compile-test:        called after javac compilation of JUnit tests
      -pre-compile-test-single:  called before javac compilation of single JUnit test
      -post-compile-test-single: called after javac compilation of single JUunit test
      -pre-jar:                  called before JAR building
      -post-jar:                 called after JAR building
      -post-clean:               called after cleaning build products

    (Targets beginning with '-' are not intended to be called on their own.)

    Example of inserting an obfuscator after compilation could look like this:

        <target name="-post-compile">
            <obfuscate>
                <fileset dir="${build.classes.dir}"/>
            </obfuscate>
        </target>

    For list of available properties check the imported
    nbproject/build-impl.xml file.


    Another way to customize the build is by overriding existing main targets.
    The targets of interest are:

      -init-macrodef-javac:     defines macro for javac compilation
      -init-macrodef-junit:     defines macro for junit execution
      -init-macrodef-debug:     defines macro for class debugging
      -init-macrodef-java:      defines macro for class execution
      -do-jar-with-manifest:    JAR building (if you are using a manifest)
      -do-jar-without-manifest: JAR building (if you are not using a manifest)
      run:                      execution of project
      -javadoc-build:           Javadoc generation
      test-report:              JUnit report generation

    An example of overriding the target for project execution could look like this:

        <target name="run" depends="jTessBoxEditor-impl.jar">
            <exec dir="bin" executable="launcher.exe">
                <arg file="${dist.jar}"/>
            </exec>
        </target>

    Notice that the overridden target depends on the jar target and not only on
    the compile target as the regular run target does. Again, for a list of available
    properties which you can use, check the target you are overriding in the
    nbproject/build-impl.xml file.

    -->
</project>

(in-package :common-lisp-user)

(defpackage "APP"
  (:use :clim :clim-lisp)
  (:export "APP-MAIN"))

(in-package :app)

(define-application-frame superapp ()
  ((numbers :initform (loop repeat 20 collect (list (random 100000000)))
	    :accessor numbers)
   (cursor :initform 0 :accessor cursor))
  (:pointer-documentation t)
  (:panes
   (app :application
	:height 400 :width 600
	:incremental-redisplay t
	:display-function 'display-app)
   (int :interactor :height 200 :width 600))
  (:layouts
   (default (vertically () app int))))

(defun display-app (frame pane)
  (loop for element in (numbers frame)
     for line from 0
     do (princ (if (= (cursor frame) line) "*" " ") pane)
       
     ;; pane is the protocol class that corresponds to a pane,
     ;; взят как аргумент функции
       
     do (updating-output (pane :unique-id element         ;; не нашёл откуда
			       :id-test #'eq              ;; взялись эти
			       :cache-value (car element) ;; опции
			       :cache-test #'eql)         ;; 
			 (format pane "~a~%" (car element)))))
;; По опциям, нашёл

;; updating-output  (stream 
;; &rest args 
;; &key unique-id     <-      здесь element как var

;; unique-id provides a means to uniquely identify the output done by body. If unique-id is not supplied, CLIM will generate one that is guaranteed to be unique. unique-id may be any object as long as it is unique with respect to the id-test predicate among all such unique ids in the current incremental redisplay. id-test is a function of two arguments that is used for comparing unique ids it has indefinite extent. 

;; (id-test #'eql) 
;; cache-value        <-      здесь element как list

;; cache-value is a value that remains constant if and only if the output produced by body does not need to be recomputed.  If the cache value is not supplied, CLIM will not use a cache for this piece of output. cache-test is a function of two arguments that is used for comparing cache values; it has indefinite extent.

;; (cache-test #'eql)          почему element то 
;;                             var то list?
;; fixed-position             element нигде не определён
;; all-new 
;; parent-cache 
;; record-type) &body body

(defun app-main ()
  (run-frame-top-level (make-application-frame 'superapp)))

(define-superapp-command (com-quit :name t) ()
  (frame-exit *application-frame*))

(define-superapp-command (com-add :name t) ((number 'integer))
  (incf (car (elt (numbers *application-frame*)
		  (cursor *application-frame*)))
	number))

(define-superapp-command (com-next :name t) ()
  (incf (cursor *application-frame*))
  (when (= (cursor *application-frame*)
	   (length (numbers *application-frame*)))
    (setf (cursor *application-frame*) 0)))

(define-superapp-command (com-prev :name t) ()
  (decf (cursor *application-frame*))
  (when (minusp (cursor *application-frame*))
    (setf (cursor *application-frame*)
	  (1- (length (numbers *application-frame*))))))