The F# Journal just published an article about lexing:
"The .NET Framework provides functions to parse primitive types including integers. These functions all adhere to the same API: the string being parsed must hold only the number. This simple API is fine for prototyping and production when performance does not matter but practical applications often lex streams of input containing numbers and, therefore, benefit from the ability to parse a number that is a substring in a given string with a specific starting index and length. This article looks at the design and implementation of a function to lex a sequence of integers from string and compares the performance with a version that uses the built-in parsing functions, finding that the bespoke solution is 9x faster..."
To read this article and more, subscribe to The F# Journal today!
Background reading on the reference counting vs tracing garbage collection debate - Eight years ago I answered a question on Stack Overflow about the suitability of OCaml and Haskell for soft real-time work like visualization: "*for real-ti...
1 month ago