Hi Jon,
Although the structure of VBA code is somewhat different from Lisp, you can
start transforming your lisp code by simply clip boarding it into the VBA
editor.
Then do some judicious searching and replacing - not necessarily with the
electronic tools..
For example
(setq x y) becomes
x = y
(if (= x y)
(something or other)
(something else)
)
becomes
if x = y then
something or other
else
something else
end if
(myfunction a b c)
becomes
myfunction a, b, c
By doing this, you take advantage of the logic you have already worked out
and you are unlikely to omit features.
I converted the Aust Rainfall lisp code to VBA in about an hour this way.
This was less time than the time it would have taken me to find the bug in
the lisp code. The program had about a hundred lines of computations, as
well as file handling.
--
Laurie Comerford
CADApps
www.cadapps.com.au
"Jon" wrote in message
news:41081ac7_3@newsprd01...
> Thanks James.
>
> BTW, your replies, to other people, in other news groups, have been a
great
> help to me.
>
> Thanks,
>
> Jon Rasmussen
>
> "James Wedding" wrote in message
> news:4107a15c$1_3@newsprd01...
> > You'll have to look into the help. The object model itself changes
> > drastically with C3D in that you go from external mdb files to dealing
> with
> > the dwg entities as data. I've found the C3D VBA API quite tidy, so I
> don't
> > think your time would be wasted in upgrading your routines to VBA.
> >
> > Just $.02
> >
> > --
> > James Wedding, P.E.
> > IT Manager
> > Jones & Boyd, Inc.
> > Dallas, TX
> > XP/1 on P4-3.4/1G
> > LDT2004&5+C3D
> >
> > Troll :a slang term for a person who posts messages without contributory
> > content, simply intended to incite conflict. http://wikipedia.com
> >
> >
>
>