Topic: What's the next Milestone for the swamp?

[Mark]

For those asking about SVN. (ask me in a PM or do a search here for 'tortoise')

[JohnK]

Well that was short lived. I guess I'm going solo again.

I'm going back in my hole. See ya.

[jbuzbee]

sad.

[JohnK]

Project <NO-NAME>; Phase: alpha (concept)
Project Green Dragon; Phase: alpha (concept)

I have set up a small scale test library consisting of ~30 functions for me to find bottlenecks, test with, and plan my documentation and standard operations with.

For this initial concept phase my goal was to establish, and follow, the traditional *nix development strategy of using a Makefile. I choose this environment for several reasons a few being; I wanted the power of building, packaging, and deployment. I also reasoned that if I created a generic makefile, it could be used in multiple situations with very little editing.

I have tested my setup on both the Windows and Linux operating systems with very little problems.

I now have a good feel for the way I want my library to operate and I have multiple choices for deliverables.

Next Step is to name this project, develop some documentation, and plan it out.

[JohnK]

I am proud to announce this project officially has a nick name...err...official code name. 

Project Green Dragon
(c) Se7en

<LOGO HERE>
If I get around to drawing one

"Green" for "reuse".
"Dragon" because it was a symbol for battle.

*blink-blink* err...umm..."Reused Battle"..."Battle--"...no, no, no..."Recycled for Battle"...yeah that will do. Now my project sounds tough!

[JohnK]

Documentation is good 'nuff and automation is solid. I have ported this project over to Linux (that means that the line endings of all the files are different--[ http://www.cs.toronto.edu/~krueger/csc209h/tut/line-endings.html ]).

If anyone has code they would like to offer up to the cause, I would greatly appreciate it.

[pkohut]

Seven, I think you took the bull by the horns...but where's the beef?

I'm confused  Autolisp, C++, Brainfuck ... Linux, DOS, Windows!?!?!?
Makefiles 

[JohnK]

yes, makefiles; they are easier for me to use right now. However bat files can be used as well as the command line when i port this back to windows.

My library is structured like the C++ STD lib.

Project Green Dragon: preprocessor doc
<snip>

File names:
.lh     =       lisp header file
.ls     =       lisp source file
.lsp    =       final product

,----[ MainFile ]-
|
| ;#include print-line.lh
|
| (defun myfoo ( / )
|   (print-line "Hello") ;; function in the "print-line" header file
|   (princ)
|  )
`----

,----[ print-line.lh header ]-
|
| (defun print-line ( str )
|   (princ (strcat "\n" str))
|  )
`----

My preprocessor will read the input file and then read the required
"include" file and thuss generate a fully assembled output file to
load into AutoCAD or copy to a network folder.

,----[ assembled file ]-
|
| (defun print-line ( str )
|   (princ (strcat "\n" str))
|  )
|
| (defun myfoo ( / )
|   (print-line "Hello") ;; function in the "print-line" header file
|   (princ)
|  )
`----
<snip>

to be honest i don't really feel like sharing any beef right now...it doesn't matter. This project was never about the "beef", it was more about the "grabbing the bull by the horns" ...but with OTHER people.  Programming is supposed to be a group activity...I'm just going through the motions here (its not fun doing this alone).

[pkohut]

Project Green Dragon: preprocessor doc
<snip>

File names:
.lh     =       lisp header file
.ls     =       lisp source file
.lsp    =       final product

,----[ MainFile ]-
|
| ;#include print-line.lh
|
| (defun myfoo ( / )
|   (print-line "Hello") ;; function in the "print-line" header file
|   (princ)
|  )
`----

Got it! Understand now 

[jbuzbee]

I tried that with compiling to .fas but my poor memory and extreme lack of documentation made management impossible.  I like your idea though.

I've got a suite of ObjectDBX based routines I would be glad to donate if you have the need.  Let me know.

[JohnK]

`Mangment' (If we are talking about the same thing) doesnt seem to be a problem; ive created and tested on a higly coupled example i created and i got very good results.

Yes please. I will take any code i can get my hands on. You will have full credit (if you would provide at least one example of how you would like your name to appear in the header i would appreciate that as well).

I will take OpenDCL code as well if you would be willing to give that up too.

[dgorsman]

Instead of creating a header defun it might be better to either expand in-place with (function...) or create a nested defun:

Code: [Select]

(defun c:foo ( / )
   (CallMyFunc arg1 arg2)#INLINE#
)

(defun c:foo ( / )
   (function
      (lambda ( arg1 arg2 / )
         ...
      )
   )
)

... or ...


(defun c:foo ( / )
   (CallMyFunc arg1 arg2)#NESTED#
)


(defun c:foo ( / )
   (defun (CallMyFunc input1 input2 / )
      ...
   )

   (CallMyFunc arg1 arg2)
)



The end result isn't as effecient (redundant functions) as hand-written but that is the typical trade-off of automation.

Appending a (defun...) at the top of the file risks be re-defined by a later file load or accidentally re-defining something already in use, neither of which would be easily found by a beginner.  Or even an expert, if the result is auto-FAS'd.

But I do like the concept.

[JohnK]

The preprocessor will ``insert'' the include file where ever you decide to place it. It will also only `insert' an include only once.

That being said, this project is really about a standard library; the preprocessor is only a custom tool for constructing the product right now.

[jbuzbee]

I will take OpenDCL code as well if you would be willing to give that up too.

Give a little time and I'll put something a little more succinct together for you.

[JohnK]

I appreciate it. Take your time.