>> So the question becomes should I be deleting all those empty files that >> contain nothing but comments and delete all the entries? Is there a >> reason >> why one can't have an empty option file? > > Never configure files names of empty or non-existent files to be > filled-in later: > > > http://www.asspsmtp.org/wiki/Empty_or_non-existent_Regular_Expressions_and_files
Thanks for the info. That's somewhat what I figured, which is why I filled in the files with some header comments, thinking that might be enough to "trick" ASSP into thinking that there was content. This begs the question if this isn't problematic then. I can forsee someone commenting out a line(s) in a file without realizing that there is no useful body left, and finding themselves with errors/problems because of empty files. Would it not be simpler to put a check in the code to validate if the file is blank, and if so, to completely ignore it? Besides, what I further can't figure out is what the difference would be between an empty config file and a blank value in the actual parameter itself. For instance, if contentOnlyRE:= or contentOnlyRE:= file:someFile.txt which is empty Both return the same value - nothing. Thanks, Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
