Re: [fpc-pascal] importtl tool

2016-10-23 Thread LacaK
To note that both "constref" are intentional. Ok I can create patch if we (you ;-)) are sure that it is okay ? -Laco. I'm not "sure" because if the flag does not tell us nothing (no IN, no OUT) I do not know if there is a "default behavior" except the "ByRef" flag and both "constref" and

Re: [fpc-pascal] C translation question

2016-10-23 Thread Lars
On Sun, October 23, 2016 2:31 pm, Bernd Oppolzer wrote > But if you translate the C for loop to a while loop first, Agree! For loops, are not nearly as flexible and powerful as while loops. For loops can get you stuck in a certain mode of thinking and you try to develop hacks to manipulate the for

Re: [fpc-pascal] C translation question

2016-10-23 Thread Lars
On Sat, October 22, 2016 4:44 am, José Mejuto wrote: > Hello, > > > It is at the end of the loop for sure, it points to the "previous" point > in the polygon and in the case of the first testing point the "previous" > one is the last one. > > So the correct code is: > > > j := i; > > This is my au

Re: [fpc-pascal] C translation question

2016-10-23 Thread Bernd Oppolzer
What I wanted to say: when translating the for loop to Pascal, you are in danger of introducing logic errors, because the Pascal for loop is kind of restricted compared to the C for loop (which is in fact simply a while loop with another notation). But if you translate the C for loop to a whil

Re: [fpc-pascal] C translation question

2016-10-23 Thread Bernd Oppolzer
it might help if I translate the C for loop into an equivalent while loop for you, (and eliminating the ++ construct), simply mechanically, without knowing anything about the application. This results in: int pnpoly (int nvert, float *vertx, float *verty, float testx, float testy) { int i, j,