Without this change then every time you read a DAOphot file it will be masked, which seems undesirable.

The code here is creating the table from scratch and returning to the user, so the user would not have already initialized a table (masked or otherwise).  In the original comment (marked for deletion) there is another alternative of adding a `masked` kwarg to `ascii.read()` to explicitly specify.  But this starts to get complicated (what to do when user says masked=False but the table requires it).  Asciitable was highly configurable in this regard, but I thought in the end it was just too complicated.  See the [table](https://asciitable.readthedocs.org/en/latest/#asciitable.NumpyOutputter) here.

I guess I would like to address this in the context of Table by ensuring it is easy to coerce a table to unmasked or masked, so at worst a user would need one additional line of code to be sure of a consistent output.  `ascii.read` is already complicated so I think it's good to avoid new kwargs.