Thinking from the perspective of encouraging people to get involved with the perl src and submit a simple patch, there doesn't seem to be an easy path from the intro docs to a recipe that shows you how. In particular, there's nothing in README or INSTALL that hints that for hacking you need to get the src from git, and once you have, what to do with it. In perl.pod there's a big scary list of "Internals and C Language Interface" pod files, but with no real indication of which ones to read first. It so happens that there *is* a quick 'how to get started' recipe in perlhack.pod, but when I first started drafting this email I hadn't found it! I looked at perlhacktut.pod as a suitable place to start, and didn't see anything. Which shows how hard it is to find. So I think what we need in README is another paragraph in the "IF YOU RUN INTO TROUBLE" section, saying: If you want to submit a patch to the perl source, see the "SUPER QUICK PATCH GUIDE" in pod/perlhack.pod. -- Never work with children, animals, or actors.Thread Next