• 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
Alessio1989

read double from, inconsistent results with some values

13 posts in this topic

I was just playing with visual studio 2013 rtm and compile some old demos to see if there were some changes to the standard library (like "max()" and "min()" functions moved to <algorithm>....)

 

And I had a little surprise with a sample code for write and read binary files with the standard library: using the following double values (111.111, 222.222, 333.333, 444.444), when I read back the data I have completely different data (like  -6.27744e+066 -6.27744e+066 -6.27744e+066 -6.27744e+066). It is also strange that the values are the same in debug mode in 32 bit and 64 bit configuration, but they change in release mode in 64 bit and 32 bit configurations. Changing the float precision model ( "precise" 80 bit, strict and fast) doesn't solve the problem.

 

Note also the sample works well if I change the double data to other values... Maybe that is due to some "nice" behaviour of the IEEE standard? ... I don't remember nothing about that in the floating point model, to me that seems just a bug (code or compiler... dunno XD )

 

Here is the code:



#include <fstream>
#include <iostream>

int main()
{
	double a[ 4 ] = { 111.111, 222.222, 333.333, 444.444 };
	double* i = new( double[ 4 ] );

	std::fstream file( "file", std::ios::out | std::ios::binary );

	file.write( ( char* )&a, sizeof( a ) );
	file.close();


	file.open( "file", std::ios::in | std::ios::binary );
	file.read( ( char* )&*i, sizeof ( double )* 4 );
	file.close( );

	for( int j = 0; j < 4; ++j )
	{
		std::cout << i[ j ] << " ";
	}
	std::cout << std::endl;

	return( 0 );
}
Edited by Alessio1989
0

Share this post


Link to post
Share on other sites

    file.write( ( char* )&a, sizeof( a ) );

 

This is incorrect. You want:

 

(char*)a

 

a is already a pointer so taking the address is bobbins.

 

EDIT: I'm surprised (char*)&a even compiles?

Edited by Paradigm Shifter
0

Share this post


Link to post
Share on other sites

    file.write( ( char* )&a, sizeof( a ) );

 

This is incorrect. You want:

 

(char*)a

 

a is already a pointer so taking the address is bobbins.

 

EDIT: I'm surprised (char*)&a even compiles?

 

here the reference is redundant since they are arrays, but that's not the problem. only with that values I got incorrect read-back from the file, with any other value, the read is correct.

Edited by Alessio1989
0

Share this post


Link to post
Share on other sites

    file.write( ( char* )&a, sizeof( a ) );

 

This is incorrect. You want:

 

(char*)a

 

a is already a pointer so taking the address is bobbins.

 

EDIT: I'm surprised (char*)&a even compiles?

No, a is an array, not a pointer, so &a is a pointer to the array. This is the same as just a in this context when the array decays into a pointer to its first element, but &a is not wrong.

Edited by Brother Bob
0

Share this post


Link to post
Share on other sites

Alessio, you still have the third incorrect parameter in your call to open(). You need to OR the last two parameters there as well.

2

Share this post


Link to post
Share on other sites

Well that's silly. a, &a and &a[0] are all the same? &a is not like the others and should really be a compiler error, if C was a sensible language (which it isn't, of course). a and &a[0] are of course the same. &a should be of type char** (since it is the address of a decayed array).

 

I guess I don't know the correct answer since I'd never use the address of an array. Taking the address of an array suggests to me it could be changed!?

1

Share this post


Link to post
Share on other sites


-6.27744e+066

That looks a lot like accidental/uninitialised memory reinterpreted as a double - the upper bytes are 0xCDCDCDCE...

 

Are you sure you are running the exact same program you have reproduced here? Apart from the missing bitwise-OR already mentioned, there isn't anything particularly wrong with your code snippet, and a compiler bug is beyond unlikely.

1

Share this post


Link to post
Share on other sites

Alessio, you still have the third incorrect parameter in your call to open(). You need to OR the last two parameters there as well.

 

thank you. now it works with that values too.

 

 

 

 


-6.27744e+066

That looks a lot like accidental/uninitialised memory reinterpreted as a double - the upper bytes are 0xCDCDCDCE...

 

Are you sure you are running the exact same program you have reproduced here? Apart from the missing bitwise-OR already mentioned, there isn't anything particularly wrong with your code snippet, and a compiler bug is beyond unlikely.

it was the comma in the input-mode of open()... anyway it is so strange, the comma don't brake me the read-back if I use other floating values.. Probably since ios openmodes are macros, some "funny" things happened...

Edited by Alessio1989
0

Share this post


Link to post
Share on other sites


it was the comma in the input-mode of open()... anyway it is so strange, the comma don't brake me the read-back if I use other floating values.. Probably since ios openmodes are macros, some "funny" things happened...

Weird. That just results in a compile error on Clang.

0

Share this post


Link to post
Share on other sites

 


it was the comma in the input-mode of open()... anyway it is so strange, the comma don't brake me the read-back if I use other floating values.. Probably since ios openmodes are macros, some "funny" things happened...

Weird. That just results in a compile error on Clang.

 

 

Pure Microsoft magic laugh.png

0

Share this post


Link to post
Share on other sites

The library that ships with MSVC apparently has an extra implementation defined parameter for (I guess) internal use. Since it has a default value, the public interface remains unchanged, but unexpected things happen when you call it the wrong way.

2

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