Closed GoogleCodeExporter closed 9 years ago
This is how IfcTimeStamp is defined in IFC4:
TYPE IfcTimeStamp = INTEGER;
END_TYPE;
Of course it is not necessary to have it signed, but the memory overhead is
very very small, unless you have millions of timestamps.
The thing is, I can not change all INTEGER's to unsinged, and I don't really
want to add item-specific changes that are not in the schema.
Or is there another reason why you want to change it?
Original comment by fabian.g...@gmail.com
on 7 Jan 2015 at 11:02
OK. I didn't realize that IfcTimpeStamp is defined as INTEGER in IFC4.
I agree with you. It is almost always better to stick to the specifications :).
Not really there is no reason. In our code, I get the time stamp which is
unsigned int and then assign to IfcTimpeStamp and got a warning message as
conversion from unsigned int to int. I will static_cast it.
Thank you.
Original comment by sajlo...@gmail.com
on 7 Jan 2015 at 11:50
Original comment by fabian.g...@gmail.com
on 7 Jan 2015 at 12:23
Original issue reported on code.google.com by
sajlo...@gmail.com
on 7 Jan 2015 at 3:58