You can optimize it all you want, in the end it's still naive because it's **wrong** : What if data spans multiple lines? What if there is some escape mechanism via `\`? What if the data can be encoded via `%xx` (byte in hex). There are not many file formats around that have no escape/quoting mechanisms. Either you write a lexer/parser or you use a premade library for the format in question.
- Nim vs. Python & Groovy (string splitting): Why is str... markebbert
- Re: Nim vs. Python & Groovy (string splitting): W... Stefan_Salewski
- Re: Nim vs. Python & Groovy (string splitting... siloamx
- Re: Nim vs. Python & Groovy (string split... erikenglund
- Re: Nim vs. Python & Groovy (string s... Araq
- Re: Nim vs. Python & Groovy (str... siloamx
- Re: Nim vs. Python & Groovy ... cblake
- Re: Nim vs. Python & Gro... Araq
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... Araq
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... jlhouchin
- Re: Nim vs. Python & Gro... federico3
- Re: Nim vs. Python & Gro... jyapayne
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... kaushalmodi
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... zetashift