Tweetovi

Blokirali ste korisnika/cu @TudorTimi

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @TudorTimi

  1. 27. sij

    Judging by the sheer amount of copy/pasted code, the developer before has probably never heard of loops.

    Poništi
  2. 27. sij

    Never noticed this, since all tools I've worked with support something like this: covergroup cg; a_x_b: cross a, b; a_x_b_x_c: cross a_x_b, c; endgroup

    Prikaži ovu nit
    Poništi
  3. 27. sij

    cover_cross ::= [ cross_identifier : ] cross list_of_cross_items cross_body list_of_cross_items ::= cross_item , cross_item { , cross_item } cross_item ::= cover_point_identifier | variable_identifier

    Prikaži ovu nit
    Poništi
  4. 27. sij

    I was today years old when I noticed that in , cross coverage that contains other crosses in the list is not allowed:

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    22. sij

    Question for folk. Does the average attendee know what Verilator is? Please retweet so I can get as much scientific (ha!) data as possible

    Poništi
  6. 22. sij

    Have one section with 10 bins, that are easily hit and at 100%? Have another sibling section with 10.000 bins, where only half are hit, hence at 50%? Well you're 75% done, kiddo, your boss is gonna be thrilled.

    Prikaži ovu nit
    Poništi
  7. 22. sij

    I like how verification planning tools assign equal weight to sections that are siblings.

    Prikaži ovu nit
    Poništi
  8. 17. sij

    Another reason is because they usually reference the code (mapped coverage), but live outside of the code, which means they very often break when the TB structure is changed (for example, moving a component to a different hierarchy).

    Prikaži ovu nit
    Poništi
  9. 17. sij

    I have such a huge aversion toward updating verification plans. One reason is because entry is done via GUIs instead of by coding.

    Prikaži ovu nit
    Poništi
  10. 15. sij

    Don't people who put all their code into one monster file get bored of scrolling around?

    Poništi
  11. 14. sij

    I also get that macros aren't good style, but copy-paste is not an acceptable alternative.

    Prikaži ovu nit
    Poništi
  12. 14. sij

    I get that most of the code was covergroups and that the language is very clunky when it comes to writing generic coverage code, but to make 10 different copies (in one case) of a covergroup just to tweak a couple of values?

    Prikaži ovu nit
    Poništi
  13. 14. sij

    12000 lines in a file!... of mostly copy-pasted code... that was not generated via some kind of script... Now I've seen everything.

    Prikaži ovu nit
    Poništi
  14. 14. sij

    Of course nothing works...

    Prikaži ovu nit
    Poništi
  15. 14. sij

    Extra level of difficulty: someone else's legacy project.

    Prikaži ovu nit
    Poništi
  16. 14. sij

    Am I the only one that dreads having to work in legacy project?

    Prikaži ovu nit
    Poništi
  17. 13. sij
    Poništi
  18. 3. sij

    Started using to test a command line application and it's awesome!

    Poništi
  19. 17. pro 2019.

    Grouping code by directory is something you can do with other aspects. Example: code for feature A? Put it in a 'feature_A' directory.

    Prikaži ovu nit
    Poništi
  20. 17. pro 2019.

    It's time to stop with these huge 'sequence lib' files. One class per file also applies to sequences. If you want to group sequences in some way, put their files in a separate directory.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·