• Top
  • Documentation
  • Books
  • Boolean-reasoning
  • Projects
  • Debugging
  • Std
  • Proof-automation
  • Macro-libraries
  • ACL2
    • Theories
    • Rule-classes
    • Proof-builder
    • Recursion-and-induction
    • Hons-and-memoization
    • Events
    • Parallelism
    • History
    • Programming
    • Operational-semantics
    • Real
    • Start-here
    • Debugging
    • Miscellaneous
    • Output-controls
    • Macros
    • Interfacing-tools
      • Io
      • Defttag
      • Sys-call
      • Save-exec
      • Quicklisp
      • Std/io
      • Oslib
      • Bridge
        • Json-encoding
        • Security
        • Command
        • In-main-thread
        • Message
        • Start
        • Bindings
        • Stop
        • Try-in-main-thread
      • Clex
      • Tshell
      • Unsound-eval
      • Hacker
      • ACL2s-interface
      • Startup-banner
      • Command-line
  • Interfacing-tools
    • Io
    • Defttag
    • Sys-call
    • Save-exec
    • Quicklisp
    • Std/io
    • Oslib
    • Bridge
      • Json-encoding
      • Security
      • Command
      • In-main-thread
      • Message
      • Start
      • Bindings
      • Stop
      • Try-in-main-thread
    • Clex
    • Tshell
    • Unsound-eval
    • Hacker
    • ACL2s-interface
    • Startup-banner
    • Command-line
  • Hardware-verification
  • Software-verification
  • Math
  • Testing-utilities

• Bridge

Bindings

ACL2 Bridge interfaces for other programming languages.

The ACL2 Bridge can probably be used from just about any programming language that has sockets.

There is a nice Ruby interface in books/centaur/bridge/ruby.

For other programming languages, implementing a client should be a very easy exercise: just read about commands and messages to understand the communication. You might look at the Ruby interface as an example.