Edit: I suppose you're talking about something more declarative like Eg. povray scripts, I'm not aware of such a thing.
Edit2: Eagle's .brd/.sch files are actually XML, FWIW, and from the git diffs I've done from time to time between commits - almost human readable (but perhaps not human writable).
Edit3: Agree with jimmyswimmy, there are so many compromises, trade-offs and optimizations going on which (for me at least) require the visual cues when placing parts and routing traces. Sometimes even the 2D visualization on the screen seems inadequate, when you get a board fabbed and see it assembled & fitted, sometimes you have that... oh damn, I wish I had seen it like that, I would have done X.
Each PCB design package has its own programming language, here's an example of what you can do with Eagle's ULP: http://irq5.io/2013/03/30/circular-layout-ulp-for-eagle/
Edit: I suppose you're talking about something more declarative like Eg. povray scripts, I'm not aware of such a thing.
Edit2: Eagle's .brd/.sch files are actually XML, FWIW, and from the git diffs I've done from time to time between commits - almost human readable (but perhaps not human writable).
Edit3: Agree with jimmyswimmy, there are so many compromises, trade-offs and optimizations going on which (for me at least) require the visual cues when placing parts and routing traces. Sometimes even the 2D visualization on the screen seems inadequate, when you get a board fabbed and see it assembled & fitted, sometimes you have that... oh damn, I wish I had seen it like that, I would have done X.