Closed caobo1994 closed 4 years ago
I believe this is the table you mentioned. I am not expecting infinite output because the row of the table is depended on |resultL| AND |resultL| will depend on how many times users run this software. However, I do decide to change the design of this table! So I will leave this post open and close after the change.
@sharyuwu, if you are displaying a table to the screen, you want to add an environment variable to represent the screen.
I like the generality that you are aiming for, but your project will be simpler if you decide in advance what scenarios you want to run for the user. They can give the start date and the end date and you can a priori decide some options to compare. As I've mentioned before, having a sequence that stores all of the results is potentially confusing. How does someone know the meaning of the ith index into resultL? If you decide what scenarios you are going to run, you can have more meaningful variable names than indexing into a sequence. This is highlighted by the fact that your table above does not have column headers. I don't think you know what to call these columns, which means the user has to keep track of the meaning of each index? I might be missing something, but I think you are still better off with a simpler design.
@smiths @caobo1994 The new design displays the table in a file. And also I rearrange the design of the table. Now I will produce two for the result.
Usually, when reading some long contents, people scroll up and down, not left and right. However, this table has infinite number of columns, but finite number of rows, so the table can be too long horizontally to be contained in one single screen. It is counter-intuitive for people to read. I suggest that you do a row<->column change, and show this table vertically.