I do not want to invite an argument about whether Pseudocode is useful or not here, there are many questions related to this. I sometimes find pseudo-code for writing useful, but one thing that comes up all the time is how best to express it?
Sometimes I end up with a numbered approach, in other cases I will use C style syntax, but in most cases it is a combination of what I think is best at the time. This is good, but after 6 months, when I come to review it again, it is not always so clear what the intention was! To combat the fact that I recently began to split the page into two parts and down the right half, I will write pidgin [Insert Language Here] and to the left I will write in really obvious and detailed English.
I don’t think there are any “Standards” for writing pseudo-code, but I’m interested in learning how other people do it, and maybe it will help me decide on a unified approach.
Thanks in advance.
Oh, I know this question is subjective, and I'm sorry if this is not the intended purpose of SO, but it is still a valid question. In fact, are there really so many calculation questions that have one correct answer? I will mark the most useful answer as correct.
source
share