I was actually leaning towards set/get to make it more distict from the read/write for memory, but that way sounds fine too.
Gabe Quoting nathan binkert <[email protected]>: >> That reminds me. Why do we have a convention of read/set? Why not >> read/write or set/get? It seems a little asymmetric, but admittedly >> probably not important enough to change in any case. > > I have no idea, but if you want to change it, I'd suggest read/write. > Maybe at some point write meant something else. I don't even recall > who did it in the first place. > > Nate > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
