Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.cad.autocad AutoLISP FAQ (part 1/2) - general
Section - [6] AutoLISP editors and other tools

( Part1 - Part2 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Cities ]


Top Document: comp.cad.autocad AutoLISP FAQ (part 1/2) - general
Previous Document: [5] AutoLISP compilers
Next Document: [7] AutoLISP problems and bugs
See reader questions & answers on this topic! - Help others by sharing your knowledge
[6.1] AutoLISP editors
  Visual Lisp by Autodesk
    see [5.3]. The best and most recommended tool. With AutoCAD 2000 it
    is included for free.
  Emacs for NT
    Huge editor and quite hard to learn but it's written and
    customizable in LISP. Free, for all platforms. Comes in two flavors,
    www.xemacs.org or the GNU emacs for NT.
    Check out http://xarch.tu-graz.ac.at/autocad/lsp_tools/ntemacs.html
  Vital LISP 
    outdated by Visual Lisp. Not available anymore
  LispLink 2000
    Commercial AutoLISP Editor with Syntax Highlight, Parenthesis 
    Checking, Project Manager, Dialog Preview, and Support for Visual 
    LISP Functions and FAS Compilation. http://www.caelink.com/
  CodeMagic
    Shareware text editor with AutoLISP syntax highlighting.

Old stuff:
  LispPad
    AutoLISP Editor by Tony Tanzillo.
  Visual LISP by WSSW
    Old small Windows LISP Editor, Version 1.0 was even free. See [1]
  WCEDIT 2.02
    Old ADS editor for DOS R12, can evaluate lisp code from within the
    editor, free.  See [1]
  CODEKEY
    Old commercial DOS IDE, internal pretty printer, protect, unprotect,
    kelvinator. Still available?
  ALLY 3.0 and CADET
    Shareware LISP Analyzer and Editor. See [6.2]
  pred
    free, small dos editor which provides parenthesis highlighting.
    At ftp://xarch.tu-graz.ac.at/pub/autocad/lsp_tools/
    A similar editor is ADE.
  LSPEDIT from xlisp-stat
    A simple free Windows Lisp editor that supports parenthesis matching and
    code indentation.
    Check out http://www.stat.umn.edu/~luke/xls/xlsinfo/xlsinfo.html

  General customizable programming editors like MultiEdit Pro,
    WinEdit, E!, PFE, TextPad, UltraEdit or PFE are widely used also.
    They usually don't provide Lisp syntax checking or pretty printing,
    but (some even regular expression) multi-file search/replace and
    customizable syntax highlighting.

  There are others not that good (ADE) nor I don't have a description
  yet.

[6.2] Analyzers, Packagers and Parenthesis checkers
  Parenthesis checkers should not be used anymore. Editors should do the
  job. Analyzers generate a function cross-reference, the calling and the
  reverse callers tree. Packagers are used to generate libraries from
  various source files, copying all the needed functions.
  There's currently no code-walker which can internationalize command
  strings, but with R15 came a lisp analyzer (LCA).

  VLISP's [5.3] compiler analyses (compile with full messages) and
    checks parens <Ctrl-Alt-C>
  Reini's AutoLISP Packager
    http://xarch.tu-graz.ac.at/autocad/lsp_tools/#Packager
    Browsable function cross-referencer, reverse calling tree, creates a
    library from source files. ("Packaging" or "Function Shaker")
  PEI Findvars
    Similar to the Packager above, but not only functions, additionally
    detects symbols to be localized. http://www.perceptual-eng.com
    I personally use this.
  RapidLisp v1.0c [new]
    Shareware Lisp analyser für R14. http://www.cps.de/cad/rapidlisp/
  AVC - AutoLISP Variable Collector [new]
    Freeware, finds all variables to be declared per function.
    http://users.actcom.co.il/sysoft/vc.htm
  LCA - Autodesk's AutoLISP Compatibility Analyzer
    On the Migration CD. Details AutoCAD 2000 compatibility issues found 
    in specified AutoLISP (LSP) or Menu LISP (MNL) files. (simple "Code Walker")

  ALLY30.ZIP (old)
    Shareware LISP analyser. Checks syntax and prints statistics, function
    dependence tree and used symbols, but no packaging. At [1]
  lck21b.zip (old)
    LCK LISP Checker 2.1b (graphical)
  paran.zip  (old)
    Simple
  PARNCH.ZIP (old)
    Simple
  There are also some AutoLISP programs which count parenthesis.

[6.3] Pretty Printers
  External:
    FMT202S.ZIP
      LISP, DCL and FRM source code formatter. Not checked yet.
    LB.EXE
      Autodesk's source code beautifier.
      In the SDK2 or at [1]. Has problems with longer strings,
      and new-style in-line comments.
    PPRINT.LSP
      In the SDK2, see [1.2], or at [1]
  Internal:
    Visual Lisp, Vital LISP, Emacs and Codekey provide internal
    beautifiers as I'm aware of it.

User Contributions:

1
Mar 17, 2023 @ 5:17 pm
Regardless if you believe in God or not, read this message!!!

Throughout time, we can see how we have been carefully conditioned to come to this point where we are on the verge of a cashless society. Did you know that the Bible foretold of this event almost 2,000 years ago?

In the book of Revelation 13:16-18, we read,

"He (the false prophet who deceives many by his miracles--Revelation 19:20) causes all, both small and great, rich and poor, free and slave, to receive a mark on their right hand or on their foreheads, and that no one may buy or sell except one who has the mark or the name of the beast, or the number of his name.

Here is wisdom. Let him who has understanding calculate the number of the beast, for it is the number of a man: His number is 666."

Referring to the last generation, this could only be speaking of a cashless society. Why so? Revelation 13:17 states that we cannot buy or sell unless we receive the mark of the beast. If physical money was still in use, we could buy or sell with one another without receiving the mark. This would contradict scripture that states we need the mark to buy or sell!

These verses could not be referring to something purely spiritual as scripture references two physical locations (our right hand or forehead) stating the mark will be on one "OR" the other. If this mark was purely spiritual, it would indicate both places, or one--not one OR the other!

This is where it comes together. It is amazing how accurate the Bible is concerning the implantable RFID microchip. Here is information from a man named Carl Sanders who worked with a team of engineers to help develop this RFID chip:

"Carl Sanders sat in seventeen New World Order meetings with heads-of-state officials such as Henry Kissinger and Bob Gates of the C.I.A. to discuss plans on how to bring about this one-world system. The government commissioned Carl Sanders to design a microchip for identifying and controlling the peoples of the world—a microchip that could be inserted under the skin with a hypodermic needle (a quick, convenient method that would be gradually accepted by society).

Carl Sanders, with a team of engineers behind him, with U.S. grant monies supplied by tax dollars, took on this project and designed a microchip that is powered by a lithium battery, rechargeable through the temperature changes in our skin. Without the knowledge of the Bible (Brother Sanders was not a Christian at the time), these engineers spent one-and-a-half-million dollars doing research on the best and most convenient place to have the microchip inserted.

Guess what? These researchers found that the forehead and the back of the hand (the two places the Bible says the mark will go) are not just the most convenient places, but are also the only viable places for rapid, consistent temperature changes in the skin to recharge the lithium battery. The microchip is approximately seven millimeters in length, .75 millimeters in diameter, about the size of a grain of rice. It is capable of storing pages upon pages of information about you. All your general history, work history, criminal record, health history, and financial data can be stored on this chip.

Brother Sanders believes that this microchip, which he regretfully helped design, is the “mark” spoken about in Revelation 13:16–18. The original Greek word for “mark” is “charagma,” which means a “scratch or etching.” It is also interesting to note that the number 666 is actually a word in the original Greek. The word is “chi xi stigma,” with the last part, “stigma,” also meaning “to stick or prick.” Carl believes this is referring to a hypodermic needle when they poke into the skin to inject the microchip."

Mr. Sanders asked a doctor what would happen if the lithium contained within the RFID microchip leaked into the body. The doctor replied by saying a terrible sore would appea (...)

Comment about this article, ask questions, or add new information about this topic:




Top Document: comp.cad.autocad AutoLISP FAQ (part 1/2) - general
Previous Document: [5] AutoLISP compilers
Next Document: [7] AutoLISP problems and bugs

Part1 - Part2 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
rurban@xarch.tu-graz.ac.at (Reini Urban)





Last Update March 27 2014 @ 02:11 PM