P
Patrick Tingen
Guest
Hmm, yes, if you look at the structure of an include file: { include-file [ argument ... | {&argument-name = "argument-value" } ... ] } It looks as if it should not be allowed to pass in a parameter without a value, otherwise the description should have read: { include-file [ argument ... | {&argument-name [ = "argument-value" ] } ... ] } So its behaviour is not a bug, but the fact that the compiler accepts it, is. BTW, these 'tips' on the page you linked should really be removed: When you have a base procedure and want to make several copies of it, changing it slightly each time, use include files with parameters. For example, at times you might only want to change the name of some files or fields used by the procedure. Instead of maintaining duplicate source files, create a single include file with the variable portions (such as the names of files and fields) replaced by {1}, {2}, etc. Then each procedure you write can use that include file, passing file and field names as arguments. One should really not be doing this anymore now.
Continue reading...
Continue reading...