T3D Release/1.0.1 Filestream Include Change
by Steve Acaster · in Torque 3D Professional · 10/20/2009 (9:10 pm) · 5 replies
EDIT:
Just to let people porting know, filestream.h has been dropped somewhere along the line of stock includes, so if you need it's services, just remember to include it yourself in your cpp file and all should be well.
{Original post below]
Not flagging this as a bug without some better evidence, but has anyone noticed something up with Filestream in Release and 1.0.1?
The above worked fine during the betas, and now it doesn't.
When using it I can no longer get the file to compile, it gives 68 errors that Filestream is an Undeclared Identifier, and the same goes for everything related to it (file, open, read, write, etc).
I had a quick look at filestream.cpp and didn't notice any difference from beta4 - though my C++ knowledge is minimal.
Issue discovered when porting this pathfinding resource to 1.0.1 from the betas.
Just to let people porting know, filestream.h has been dropped somewhere along the line of stock includes, so if you need it's services, just remember to include it yourself in your cpp file and all should be well.
{Original post below]
Not flagging this as a bug without some better evidence, but has anyone noticed something up with Filestream in Release and 1.0.1?
FileStream file; file.open(fname, Torque::FS::File::Write);
The above worked fine during the betas, and now it doesn't.
When using it I can no longer get the file to compile, it gives 68 errors that Filestream is an Undeclared Identifier, and the same goes for everything related to it (file, open, read, write, etc).
I had a quick look at filestream.cpp and didn't notice any difference from beta4 - though my C++ knowledge is minimal.
Issue discovered when porting this pathfinding resource to 1.0.1 from the betas.
About the author
One Bloke ... In His Bedroom ... Making Indie Games ...
#3
A simple, include of core/stream/filestream.h was all that was required.
Have dericious caek - I hope you like marzipan...
I've no idea why someone would want to make a Battenburg cake simulator ... but I'm glad that they did
10/20/2009 (10:59 pm)
Tricorn hats off to you, my good fellow.A simple, include of core/stream/filestream.h was all that was required.
Have dericious caek - I hope you like marzipan...
I've no idea why someone would want to make a Battenburg cake simulator ... but I'm glad that they did
#4
10/20/2009 (11:09 pm)
OT: Cool cake simulator =P 
#5
In general this is a good thing to keep your build times down and reducing dependencides.
10/21/2009 (2:23 am)
It was probably something i changed. I often remove unnessasary #includes when i find them and fix things up with pre-declarations of classes.In general this is a good thing to keep your build times down and reducing dependencides.
Torque 3D Owner Joshua Halls (Xerves)