Lutz,
May we have a fast scanf-style reader to parse input in the next release? Something the opposite of format, perhaps?
Quote from: "Jeff"
Lutz,
May we have a fast scanf-style reader to parse input in the next release? Something the opposite of format, perhaps?
I second that.
Did you read my other post about using (read-line) for getting input from user? You can combine that and regular expressions with 'regex' or 'parse' to parse out the components from the input.
Quote from: "Lutz"
Did you read my other post about using (read-line) for getting input from user? You can combine that and regular expressions with 'regex' or 'parse' to parse out the components from the input.
Lutz,
I did. Thank you again. I can't believe I missed that in the manual! :-)
Thank you for creating and sharing newLISP too!
It is what I have been looking for. The first LISP that I began to feel comfortable with (after much pain) was Emacs Lisp. But newLISP is now my favorite.
I know, but scanf is faster, more exact, defines types, and uses *much* less memory. Which is why programs still use scanf over regex in many scenarios. Scanf gives me complete control over user input and guarantees that I get either the correct input and input types or that I get nothing at all.