thanks, your analysis of the code has helped me understand it. I hadn't realised the code lines up 8 queens on the 1st rank. This makes it a bit easier to understand.
But before I fully go thru it again, at the moment I've got stuck on a problem I thought I'd sorted 2 days ago :
creating break points in pycharm.
Last time i was working with pycharm I could just click on the line number to create what I thought was a breakpoint, I think it was represented by a red or orange ball. It worked at the time.
Today that functionality has vanished. Can't point an click anymore. The pycharm online documents say to create breakpoints with 'ctrl F8' but when I hold this down on a selected line, nothing happens.
edit: ah, just posting about it here has made the difference.
in my previous language I'd click on an empty line and write in 'stop' to get the debugger to stop at that line.
In python its not possible to use an empty line a debugger breakpoint. It nuances like this that I spend alot of time on!
But before I fully go thru it again, at the moment I've got stuck on a problem I thought I'd sorted 2 days ago :
creating break points in pycharm.
Last time i was working with pycharm I could just click on the line number to create what I thought was a breakpoint, I think it was represented by a red or orange ball. It worked at the time.
Today that functionality has vanished. Can't point an click anymore. The pycharm online documents say to create breakpoints with 'ctrl F8' but when I hold this down on a selected line, nothing happens.
edit: ah, just posting about it here has made the difference.
in my previous language I'd click on an empty line and write in 'stop' to get the debugger to stop at that line.
In python its not possible to use an empty line a debugger breakpoint. It nuances like this that I spend alot of time on!