mailman3.common-lisp.net
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

clpm-devel

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
clpm-devel@common-lisp.net

September 2021

  • 2 participants
  • 1 discussions
Suggestion to make CLPI files easier to process outside CL
by John Cowan 12 Sep '21

12 Sep '21
Rather than allowing any CL S-expression (except that all symbols must be keywords), I propose that you allow only a more restricted variety of S-expressions so that they can be readily read and processed in any other language, while being compatible with a whole bunch of Lisp's read (without full validation) and print/write functions. Specifically I propose POSE < https://github.com/s-expressions/pose/blob/master/README.adoc#specification>, which allows only a restricted set of symbols, arbitrary integers, floats, and strings, and lists. (Most of that page is the rationale, which does not need to be read unless it interests you). Code is provided to parse POSE in many languages, but the CL is not up to date, as it does not yet handle keywords, only colon-free identifiers. (But of course there is no reason not to use your own code if you want.)
2 2
0 0

HyperKitty Powered by HyperKitty version 1.3.12.