• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
gasto

"Wrapping"? Why is it not called "trimming"?

6 posts in this topic

Why is type conversion in C(akin languages)from a higher to a lower precision type not called "trimming" instead of "wrapping"?

 

It makes more sense, since in little endian systems the least significant byte(s) is(are) [b]trimmed[/b] while the rest(most significant)byte(s) is(are) cut off.

 

In fact, the wrapping takes place in bit shifting operations.

1

Share this post


Link to post
Share on other sites
Let's say you have 16-bit shorts and 32-bit ints. If you cast an unsigned int to an unsigned short,

for 0 you get 0,
for 1 you get 1,
...
for 65535 you get 65535,
for 65536 you get 0,
for 65537 you get 1,
...

In that sense, the numbers wrap around at 2^16. That's how I understand it.
1

Share this post


Link to post
Share on other sites

C is not only for little endian machines. C actually specifies undefined results when trying to store a value larger than a variable can fit. So char c = 1000 leaves c in an undefined state on machines where char is 8 bits.

 

The practical effect of most implementations is that the value wraps in the exact same way that integer overflows occur. This is only a side effect of implementation details though, and is not guaranteed behavior in C. The frequency with which projects rely on this behavior does suggest it is unlikely to change wherever it exists today, but it's still just an implementation detail.

 

And I hope trimming never catches on to explain this process. Trimming implies a far more invasive process in my mind (trimming trailing/leading whitespaces for example).

0

Share this post


Link to post
Share on other sites

The practical effect of most implementations is that the value wraps in the exact same way that integer overflows occur. This is only a side effect of implementation details though, and is not guaranteed behavior in C. The frequency with which projects rely on this behavior does suggest it is unlikely to change wherever it exists today, but it's still just an implementation detail.

 

It is actually guaranteed to behave this way for unsigned types. For signed types, overflow is UB, though on any system you'll encounter today it will probably either wrap around (2's complement) or saturate (most DSPs?).

1

Share this post


Link to post
Share on other sites
I don't think I've ever heard it referred to as 'wrapping'; 'cast' or 'convert' sure but never 'wrapping'.

The only time I've heard wrapping used is in cases of, well, wrapping such as an unsigned int at max wrapping around to zero when being added to and the like.
2

Share this post


Link to post
Share on other sites

It is actually guaranteed to behave this way for unsigned types. For signed types, overflow is UB, though on any system you'll encounter today it will probably either wrap around (2's complement) or saturate (most DSPs?).

That's not quite right. Specific behavior depends on language. In C++ with unsigned integer destination types, the result is always the least integer modulo congruent to the source integer modulo 2^n where n is the number of bits in the destination type. For a signed integer type, if the source integer value can be represented by the destination type, the value is unchanged. However, if not the result is implementation defined, not undefined.

C acts a lot like C++, other than weird wording in the standard; however, if the destination is a signed type and the original value cannot be represented in the destination type, the result can be an implementation defined value or an implementation defined signal can be raised.

C# on the other hand, for narrowing conversions that cannot be represented in the destination type, the result depends on whether or not overflow detection is enabled. If so, a narrowing conversion for an integer value that cannot be represented in the destination type will throw a System.OverflowException. If overflow checking isn't on, the result always consists of discarding the most significant bits of the source.
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0