"Kyle J. McKay" <mack...@gmail.com> writes: > If you mean for all the strchr etc. calls, multiple tables would be > required since URL_SCHEME_CHARS and URL_HOST_CHARS partially overlap,
The entries of the table could be at least 8-bit wide, so there shouldn't be any problem, should there? > but it could be done. Is the speed of strchr that much of a concern? > The code will only be invoked for http.<url>.* option settings in any > case and I expect the user would have to set an awfully large number > of those to even begin to notice. We can start slow and then optimize, but I suspect that there are sufficient number of people who are into micro-optimizing, and such a slow implementation may quickly be replaced. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
