On 3/14/20 10:18 AM, fredvs via fpc-pascal wrote:
Yes, that is the main problem.
If you do it the "logical" way, placing at first without initialization,
when ord(kind) is used in code, because the order has changed, lot of code
must be re-written.
i don't see a problem with that... only some time to fix ugly/bad code...
But if you place it at last you only have to initialize at creation with
nk_none and replace all use of "high(enumty)" by the last - 1 item of the
enum.
the problem with this is "do you leave it last always and insert new values
before it?" OR "do you put it last now and leave it there when adding new values
after it?"
much better to put it first in the list for numerous reasons...
--
NOTE: No off-list assistance is given without prior approval.
*Please keep mailing list traffic on the list where it belongs!*
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
