Re: simple URL GET

> > What errors, if any, do you get from these? DEXADOR: SBCL: (dex:get "https://planet.lisp.org";) debugger invoked on a CL+SSL:SSL-ERROR-VERIFY in thread ... ((LAMBDA (CL+SSL::OK CL+SSL::CTX) :IN "/Users/tarvydas/quicklisp/dists/quicklisp/software/cl+ssl-20211230-git/src/context.lisp") 0 #.

simple URL GET

I want to GET a URL and put the result into a string with as little fuss as possible, but nothing seems to work. I am trying to follow: https://lispcookbook.github.io/cl-cookbook/web-scraping.html using SBCL and LispWorks. I'm on a MacBook (Ventura) and am getting SSL errors (plus unicode error

Re: Numpy and Common Lisp?

"If you specifically want numpy, it may be possible to have Common Lisp talking to python." CL can run python (uiop:run-program "python3 ~/quicklisp/local-projects/clvpy/hello.py" :output t) This isn't 1950 anymore. 1950s biases about what "efficiency" means no longer apply. (Lisp used to be

Re: Prototype Based Programming in Lisp?

On 16-07-05 02:33 PM, Alexandre Rademaker wrote: On Tue, Jul 5, 2016 at 3:06 PM, Paul Tarvydas <mailto:paultarvy...@gmail.com>> wrote: On 16-07-05 01:31 PM, David McClain wrote: I strongly recommend Rob Pike's talk "Concurrency is not Parallelism - It's B

Re: Prototype Based Programming in Lisp?

On 16-07-05 01:31 PM, David McClain wrote: Hi Paul, Please forgive my ignorance, No sweat :-). but don't the things you advocate require access to, or rewriting of, the JS Server side? Or are you performing this magic from the client side? That’s all I have access to in these foreign tools.

Re: Prototype Based Programming in Lisp?

On 16-07-04 04:08 AM, Kenneth Tilton wrote: On Sun, Jul 3, 2016 at 10:18 PM, David McClain mailto:d...@refined-audiometrics.com>> wrote: Hi Ken, I think I see what you are recommending. But one of the facts of these external programs is the lack of multi-processing in their

Re: Naming suggestions

Actually, I see this as a dereference operator, not a reference operator. In C, the reference operator is &, and dereference is * ... pt

Re: Erlang style processes in Common Lisp

I apologize for my absence. @David - FBP == flow-based programming. http://www.jpaulmorrison.com/fbp/ http://www.amazon.ca/Dataflow-Reactive-Programming-Systems-Practical/dp/1497422442/ref=pd_sim_14_1?ie=UTF8&refRID=0KS3EMGV9M1T5D66DCNG Frame-based is interesting in its own right, though http

Re: Erlang style processes in Common Lisp

I've been trying to convince the people over the in FBP group that this is much easier than it sounds (esp. if you're rolled your own RTOS, as I have done many times). (I have to leave now, but will answer in more detail later tomorrow). Here are some slides for a not-yet-presented talk: http

Re: Should GC hooks be used to help broken software?

On 15-07-04 07:30 AM, Elias Mårtenson wrote: The following question was raised during my development of an asynchronous library I'm currently building for RabbitMQ. Aside / rhetorical: Are you trying to achieve a certain level of "efficiency"? If

Re: [pro] Lexer wanted

performance of Esrap vis-a-vis something like cl-yac? Given a BN > grammar, how hard is it to build up a PEG parser? > > thanks, > > >> On Feb 13, 2015, at 10:04 AM, Paul Tarvydas wrote: >> >> Esrap is a PEG parser. PEG is Lex and Yacc combined. I'm sure

Re: [pro] Lexer wanted

Esrap is a PEG parser. PEG is Lex and Yacc combined. I'm sure that you could use esrap as a lexer-only, if you wish to. http://nikodemus.github.io/esrap/ On my github there's an experimental PEG syntax overlaid over esrap syntax, if you care. https://github.com/guitarvydas Ping me if you

[pro] write-char vs. 8-bit bytes

I'm using sbcl to write-char a 16-bit unsigned integer to a socket as two separate unsigned 8-bit bytes, for example 141 should appear as #x00 #x8d. SBCL appears to convert the #x8d into a two-byte utf-8 char, resulting in 3 bytes written to the stream \#x00 #xcd #x8d. What is the proper in

Re: macro returning more than one form

@All, thanks for the interesting discussion. Certainly gives me something to chew on. Re-reading the responses, I see that, while I did sort-of say it, I didn't emphasize the point of this: I have a PEG-syntax parser written in esrap. I am binding at least two such parsers as reader-macros

Re: macro returning more than one form

On 14-03-14 12:57 PM, Pascal J. Bourguignon wrote: I'm writing diagram-compilers that emit CL. It seems to me that each emitted lump of code should be in it's own package. Am I thinking about this "wrong"? I also have similar issues using a PEG parser (a PEG syntax for esrap) inside a keyb

Re: macro returning more than one form

On 14-03-14 12:00 PM, Dave Cooper wrote: ... What does LW and SBCL hate about wrapping toplevel forms in progn? The LW debugger can't set breakpoints unless I remove the progn wrapper. A user of my code is complaining that "it doesn't work" in SBCL (:-) (I guess I'll get more detail later).

Re: macro returning more than one form

Alessio, Steve, Yes, I intend the first form to be an (in-package ...) followed by a (defun ...). My immediate problem is solved, thank you! I am currently writing the result out to a file anyway, so I can easily strip the progn on the way out. But, now I'm curious. Is there a reasonable

macro returning more than one form

What is the best way to write a macro that returns more than one form to the top level? E.g. (in-package :xxx) (defun ...) I've been wrapping a progn around the result, but LW doesn't like it very much, and SBCL seems to hate it. Thanks pt

STM advice

I'm about to look into Software Transactional Memory techniques for some financial code I'm involved with. Any advice about which libraries to look at (and why) would be quite welcome. Thanks pt

Re: [pro] Lisp and DSLs

It seems to me that most people don't understand the rudiments of CL's ability for creating DSL's and live in the land of Blub. If you're going to discuss creation of DSLs, it might be an idea to first relate the aspects of CL using compiler terminology. Here are some random thoughts (not all a

Re: [pro] Is cl-yacc going to cut it?

> symbol parse, but is there another general parsing technique, available > as a lisp library of course, that either works at a lower level than > yacc usually does or allows the lexer to access more context about the > parse? The relatively new PEG packrat parser technologies make it possible to

Re: [pro] The Best Examples of "Code is Data"

> On 09/06/2010 12:41 PM, *Paul Tarvydas* wrote: > > 1. Doug Hoyte's book Let Over Lambda, chapter 6.3 Alet and Finite State ... > I've read his treatment of state machines, and they seemed like simplified > co-routines. Or are you just referring to his macro techni

Re: [pro] (values) for for-effect functions

At least in LW, (values) returned to the REPL stops the repl from printing anything. I've used it when the value otherwise returned would print something big (and long). I would expect to see it in (a) functions called at the top level and (b) in places where "nothing" returned vs. "something"