<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Hi Lloyd, I understand your points, but I think we'll have to agree to disagree on this one! Even just looking at the index to the re module docs, you get "compile, inspect, replace, run, split", and that really is pretty much all there is to it. I mean, you write a regex, you compile it, you run it on a string and check the matches. Maybe you split them or replace segments of them with it. That's it. The rest is either regex syntax or language-specific implementation detail / configuration options. Regex syntax documentation and tutorials are very widely available, and the details of the erlang implementation are comprehensively specced in the appropriate place in the docs.</div><div class=""><br class=""></div><div class="">I don't really want to get into the whole community/expansion can of worms here, because I feel like it's been implicitly done to death in The Other Thread(!) - but my personal view is that if people decide to reject erlang (and OTP!) because its regex docs are too terse, well, uh, that's a shame for them, because that's *really* not what it's about. I think the fact that the regex docs are so terse (read: limited to describing the erlang PCRE implementation/wrapper, on the assumption that regex documentation is available elsewhere) is indicative of that.</div><div class=""><br class=""></div><div class="">Best</div><div class="">Igor</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 30 Jan 2021, at 19:32, Lloyd R. Prentice <<a href="mailto:lloyd@writersglen.com" class="">lloyd@writersglen.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Sorry guys, I do understand regular expressions well enough to use them the rare times when I need them. I have read PCRE docs and various others and I would say that they are generally better written and presented than the re reference doc. And I do understand that regular <span style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);" class="">expressions and Erlang are two completely different languages.</span><div class=""><br class=""></div><div class="">If the community is satisfied with the docs as they are then there’s nothing more to say.</div><div class=""><br class=""></div><div class="">But I do contend that there’s a problem. Software docs need to be fit for purpose. In-line code comments, library references, tutorials, and technical white papers are all different formats with different functions and conventions. A language needs them all to attract and sustain a robust community. My read is that the re doc conflates these functions in a confusing and distracting text that well may discourage folks new to Erlang.</div><div class=""><br class=""></div><div class="">Assertions:</div><div class=""><br class=""></div><div class="">— Erlang is a tool.</div><div class="">— The value of a tool is the efficiency and effectiveness with which it solves real-world problems.</div><div class="">— As programmer, time is our most precious asset.</div><div class="">— A software library that is inadequately documented likely wastes our time when we first strive to understand why and how to use it, when we seek to refresh our memory of how to use it, and when we wish to extend it’s functionality.</div><div class=""><br class=""></div><div class="">When I turned to re to solve a problem at hand, the re doc was 90 percent a waste of my time. And that, sorry to say, diminishes the value of Erlang for me as a tool.</div><div class=""><br class=""></div><div class=""> I’m wondering how many others may have had the same experience. And how many of those have rejected Erlang as too much bother to learn.</div><div class=""><br class=""></div><div class="">Best wishes,</div><div class=""><br class=""></div><div class="">LRP</div><br class=""><div dir="ltr" class="">Sent from my iPad</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On Jan 30, 2021, at 1:22 PM, Igor Clark <<a href="mailto:igor.clark@gmail.com" class="">igor.clark@gmail.com</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="ltr" class="">Hi Lloyd, tbh it sounds like you’re mostly having problems with regular expressions rather than the erlang docs for it. It’s a pretty dense subject, and unless you’ve already got a way up the learning curve, the syntax can appear arcane. Not only that but the way they are used and implemented in different systems is complex and unpredictable.</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Thing is once you’ve got your head round the basics by working through some regex-specific docs, then the docs dealing with the specifics of a given language’s implementation will make a lot more sense.</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">I don’t think it’s really fair to criticise the erlang re docs without really grasping the meat of the subject it’s discussing, because it’s not there to teach regular expression purpose and syntax, rather the way to use it in the erlang re library. You wouldn’t criticise a Haines VW Golf manual for not explaining what a carburettor is :-)</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">I’d suggest the “quick start” at <a href="https://regular-expressions.info/" class="">https://regular-expressions.info/</a> to get you off the ground, and the site is a great reference later on as well. The classic book to get if you want a really clear non-screen version is the O’Reilly “Mastering Regular Expressions” by Jeffrey Friedl - in spite of the title it starts from the ground up and doesn’t assume any prior knowledge. Many happy hours spent poring over that tome!</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Cheers</div><div dir="ltr" class="">Igor</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On 30 Jan 2021, at 17:43, Lloyd R. Prentice <<a href="mailto:lloyd@writersglen.com" class="">lloyd@writersglen.com</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class=""><span class="">Hi Dieter,</span><br class=""><span class=""></span><br class=""><span class="">Thanks for the question. </span><br class=""><span class=""></span><br class=""><span class="">I don’t like to criticize without having something constructive to contribute. Let me start by saying that I do understand that documentation of software is difficult for many reasons. Nevertheless, here are crucial questions we must ask when we set out to write documentation, indeed, write anything:</span><br class=""><span class=""></span><br class=""><span class="">— Why am I writing this?</span><br class=""><span class="">— Who am I writing this for?</span><br class=""><span class="">— What is the context in which this will be read?</span><br class=""><span class="">— What would I like my readers to gain by reading this work?</span><br class=""><span class="">— What do my readers already understand?</span><br class=""><span class="">— What style/formatting conventions do my readers expect?</span><br class=""><span class="">— Have I structured my work logically?</span><br class=""><span class="">— Have I drafted my work as clearly and concisely as I know how?</span><br class=""><span class="">— Will my readers understand the technical terms or trade jargon that I’m temped to use?</span><br class=""><span class=""></span><br class=""><blockquote type="cite" class=""><span class="">...it has a nice interface, just a few functions with clear names.</span><br class=""></blockquote><span class=""></span><br class=""><span class="">My guess, Dieter, is that the re doc works for you because you already have enough knowledge and experience to understand, say, when, where, and why you would want to compile a Regexp or run a (Subject, re). So, you scan down and see compile/1 and your needs are met. But you did have to scan down through some 14 blocks of dense text to find compile/1|2. But— given your need to refresh your memory about use of the compile/1|2 functions, did you really need to scan over the second and third paragraphs under Description? Maybe these should be a footnote.</span><br class=""><span class=""></span><br class=""><span class="">As one who comes to Erlang re with less experience— I’m totally baffled by compile/1, inspect/2, and run/2|3. What in the world are they? How can they be useful to me? I can kind of sus replace/3|4 and split/2|3, but geez man, all that fine print is brain numbing. And most of the text from Perl-Like Regular Expression Syntax on down looks to me like a tutorial and densely written at that. Do I really need to know that stuff to program, say, an Erlang markdown interpreter? </span><br class=""><span class=""></span><br class=""><span class="">I could say much more. But my take is that the re doc tries to convey much more information than warranted by a reference doc. This suggests, perhaps, the need for additional documentation such as a cookbook-like re tutorial for Erlang noobies and a technical white paper or some such for folks who need to get their hands greasy with internals.</span><br class=""><span class=""></span><br class=""><span class="">As I scan down through the list of Erlang standard libraries I see any number of which I’d apply the same critique. So an offer to standard library doc writers: Show me when, why, and how to use your library, and I’ll do my best to help you write clear documentation. </span><br class=""><span class=""></span><br class=""><span class="">LRP</span><br class=""><span class=""></span><br class=""><span class="">Sent from my iPad</span><br class=""><span class=""></span><br class=""><blockquote type="cite" class=""><span class="">On Jan 30, 2021, at 12:30 AM, Dieter Schön <<a href="mailto:dieter@schoen.or.at" class="">dieter@schoen.or.at</a>> wrote:</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">Good morning,</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">I just looked at the erlang re documentation and I think it has a nice interface,</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">just a few functions with clear names.</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">I always have trouble to remember which of python's re.match and re.search does what.</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">For my taste, there are also enough examples included. Just the PCRE options are a bit overwhelming.</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">It would help if you could elaborate on the areas where you have problems.</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">Kind regards,</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">Dieter</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">On 28.01.21 23:26, Lloyd R. Prentice wrote:</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">I’ve used regular expressions including Erlang regex off and on over the years—enough to get the job done but barely enough to claim competence.</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">But I’m sorry— the documentation for re is total inside baseball. Can’t make heads nor tails.</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">Can someone please please suggest or write a tutorial with lots of examples for mortals who just want to get the job done?</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">Happy to collaborate but can only contribute my ignorance.</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">All the best,</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">LRP</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">Sent from my iPad</span><br class=""></blockquote></blockquote><span class=""></span><br class=""></div></blockquote></div></blockquote></div></div></blockquote></div><br class=""></div></body></html>