The expansion of texpropcode in r37108 (Mattias) breaks fppasjs because it defines an array with texpropcode as range.
This prohibits building of trunk.

Mailing lists / fpc-devel / 2017-09
7 messages · 6 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
The expansion of texpropcode in r37108 (Mattias) breaks fppasjs because it defines an array with texpropcode as range.
This prohibits building of trunk.
Hi,
Marco van de Voort wroteThe expansion of texpropcode in r37108 (Mattias) breaks fppasjs because it defines an array with texpropcode as range. This prohibits building of trunk.
Sven fixed it already in r37109.
(The quick-response advantage of receiving build notifications from Marcus' Jenkins... ;)
Charlie
The expansion of texpropcode in r37108 (Mattias) breaks fppasjs because it defines an…
The expansion of texpropcode in r37108 (Mattias) breaks fppasjs because it defines an array with texpropcode as range. This prohibits building of trunk.
Sorry. I forgot to commit a file. I see that it is already fixed in trunk.
Mattias
Sven fixed it already in r37109. (The quick-response advantage of receiving build…
Am 02.09.2017 17:06 schrieb "Karoly Balogh (Charlie/SGR)" <
it
Indeed :)
Regards,
Sven
Hi,
trunk is always broken, is it not?
Perhaps that is why it is called trunk. After all a trunk is an incomplete tree. Just a little bit more than a completely broken tree (stump)
Best,
Benito
Benito van der Zander wroteHi, trunk is always broken, is it not?
Huh? It's rather seldom that we have real build breakages and even then more often than not only on certain systems.
Regards,
Sven
Sven fixed it already in r37109. (The quick-response advantage of receiving build…
Maybe we can create a new fpc mailing list fpc-notifications or something like this so everybody can subscribe if needed?