Block diagram for PIC based mp3 player

[Ioannis]

Well, about that C stuff, C in general forces you to be a better programmer, having to structure your program more efficiently. Also forces you to use functions, the equivalent of a subroutine, but more efficiently. For example, calling a function in C, lets you pass variables that really aren't used before and won't be used after. So memory is really conserved that way.

In Basic compiler this is not the case. You have to declare the variables that are going to be used and they reserve their location permanently.

Other than that, I think it is up to the compliler to be as much efficient as possible.

See how Fred Eady managed to convert C routines to PBP and create TCP/IP stack:

http://www.edtp.com/downloads.htm

And Trent, yes. The C example you post has nothing different from the respective PBP one.

Only that C programmers when see a goto are getting crazy. So I would use at PBP also the same while 1/wend to cool them down! At the produced ASM code level, it is really the same, so what's the fuzz about?

Ioannis

[T.Jackson]

Well, about that C stuff, C in general forces you to be a better programmer, having to structure your program more efficiently. Also forces you to use functions, the equivalent of a subroutine, but more efficiently. For example, calling a function in C, lets you pass variables that really aren't used before and won't be used after. So memory is really conserved that way.

In Basic compiler this is not the case. You have to declare the variables that are going to be used and they reserve their location permanently.

That's an excellent explanation that makes a lot of sense.