David, I have been a fan of custom constants since I started using 4D, probably because my background in C meant that I couldn’t imagine a programming environment which didn’t have them (whether as preprocessor directives or enumerations).
I think some of your suggestions are wonderful. RELOAD CONSTANTS would be great to have while developing. But a couple puzzle me. Boolean constants: why? What more than True and False do you need? Removing constants from compiled / distribution code. For completed databases, yes. For components, no: I use constants exported from components as a way of communicating with them, as selectors or parameters. I remember being bewildered when I started using 4D that the 4D Chart didn’t using constants for the huge array of selectors passed to its routines, but needed me to remember numeric selectors. But I must confess to being a monster, sadly. Jeremy Jeremy Roussak [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
