On Jun 3, 2008, at 2:28 AM, Gabe Black wrote:
I put bugs in quotes because I'm not sure if these are bugs, I'm
just using things wrong, or it's supposed to work that way. First,
if there's no default value for a parameter, it seems that objects
created with that parameter won't recognize assignments or
manipulation to that parameter. In my case I was doing something
that wouldn't work without a default value anyway, but what might
fail more intuitively would be to create the parameter but assign it
the value None. Then if you tried to use it uninitialized, it would
complain that type None has no attribute whatever, or whatever it
says specifically, rather than insisting that the parameter doesn't
exist.
I haven't see the problem you describe. It seems to work for me,
however if you don't specify a default value M5 should require you to
have one before it will instantiate that object, which for some reason
it doesn't at the moment.
Second, I noticed that if you don't assign the type field to be the
same as the name of the class it's in, no param header file is
created. I really don't know what that's from and I don't think I'm
qualified to figure it out, but that doesn't seem like something
it's supposed to do. If that's using it incorrectly then maybe there
should be an error message or something?
What does the class it's in mean? The type needs to be assigned to the
name of the C++ object that will be created with that particular
params class. If you don't do that I wouldn't expect it to work at
all. What do you think it's supposed to do?
Ali
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev
