Re:A fast HTTP request/response parser for Common Lisp
by PuercoPop on Thursday October 30, 2014 @09:28PM
(#8536852)
out of curiosity, what did you found horrible about string handling?
Re:A fast HTTP request/response parser for Common Lisp
by negativeview on Thursday October 30, 2014 @09:39PM
(#8536875)
So I just looked up Common Lisp string handling and none of it looks familiar. It's possible what I was trying to use before wasn't Common Lisp. It's also possible I was trying to learn from a site that was just doing a horrible job of it. It's possible things have gotten much much better since I last tried to learn it.
Whatever the cause, I was under the impression that you essentially had to treat strings as lists of characters and that there really weren't any built-in functions to handle strings as strings. It seems that's wrong at least in modern day.
Re:A fast HTTP request/response parser for Common Lisp
by aerique on Friday October 31, 2014 @04:39AM
(#8537825)
Strings are sequences and functions that work on sequences work on strings as well. So getting substrings etc. is all possible.
I've had very little problems operating on strings in Common Lisp (all I missed was starts-with and ends-with functions), could you give some concrete examples so that I might help you?
Re:A fast HTTP request/response parser for Common Lisp
by negativeview on Friday October 31, 2014 @11:22AM
(#8539193)
I can't now because it was years ago I was having problems. I'm starting to think that it was a different Lisp and not Common Lisp I was looking at, too. Too long ago to remember for sure.
Re:A fast HTTP request/response parser for Common Lisp
by PuercoPop on Thursday October 30, 2014 @09:56PM
(#8536921)
Strings are a simple-array of characters and functions that work sequences work on strings (ej. remove). They are complemented with a some string specific functions like string-equal, string-trim, string-upcase, etc. It has been that way for at least 20 years. It might have been that the site was doing a horrible job at explaining it.
It sounds like there's someone with a lot of skill working to fix exactly this.
Now, do I have time to look into Lisp again...