Return to Video

Control over Logging cs348 unit8

  • 0:01 - 0:04
    Let's make the following assumption. By some means, we have already solved the
  • 0:04 - 0:09
    problem of the formatting. The inconsistencies you've seen before we solved in
  • 0:09 - 0:14
    some manner. We still have a significant part of problem, control of energy.
  • 0:14 - 0:19
    You don't want to print out all this information all the time. It is too much.
  • 0:19 - 0:23
    You get huge log files and it's just too much to handle. You only want to see
  • 0:23 - 0:27
    what you need for a certain purpose. So, how are we going to do this? The
  • 0:27 - 0:30
    question is, what is the best option to control how much information is
  • 0:30 - 0:35
    currently being logged? Here are three choices. You can use compiler flags,
  • 0:35 - 0:39
    right? So here, you have a flag that says turn certain things on, or turn
  • 0:39 - 0:42
    certain things off that will be built into the compile process of the
  • 0:42 - 0:50
    environment. The second option is to hand count just the particular test. Soon
  • 0:50 - 0:53
    configuration sets in, but want to see these messages but not those and so
  • 0:53 - 0:58
    forth. The final option is use aspect oriented programming, right? Where you
  • 0:58 - 1:02
    could overwrite methods that print out certain things and replace it with an
  • 1:02 - 1:05
    empty string or other means.
タイトル:
Control over Logging cs348 unit8
Team:
Udacity
プロジェクト:
CS348 - Functional Hardware Verification
Duration:
01:06

English subtitles

改訂 Compare revisions