Front page | perl.perl5.porters |
Postings from September 2009
Here is a refinement of what I proposed a week ago. I'll do what Yves, and Merijn said, and list every property, with a mark to indicate those whose use is discouraged. I propose turning this into a pod file, say perluniprops.pod. Then we can replace the long and incomplete lists in perlunicode.pod by a link to this machine-generated file, which will cut down on the maintenance. If that is acceptable, it brings up some more questions. In what directory should mktables create the pod file? Perhaps it should be in the current directory, and symbolically linked to from the pod directory. I see that some pods are symbolically linked on my Linux system. Apparently you guys have some cross-platform way to do this. If that is the way to go, how do I find out how to set such a thing up? And perhaps it shouldn't generate this file each run, but only under an option, say -makepod?Thread Next