ATL / WTL / STL

sunny.rana wrote:

I am kinda very new to ATL and MFC programming i am kinda trying to control my stage motor connected to serial/com port using a sample software available online by activexperts.com it worked fine for abt month but now i guess the software a way to check evalution period which has expired so my software doesnt wrk anymore can anyone please help as to how i can work around this as i am a biomed engineer and really dont understand coding very well i have attached my code for refrence. It asl me to include 3 files i downloaded from their website.

jens rasmussen wrote:

After having allocated a new node-object, why does one use value_allocator.construct() to construct the value instead of just passing it by assignment? I have checked out the SGI and GNU implementation of stl_tree.h, and they just use assignment for bool, size_type and pointer values,

jens rasmussen wrote:

- After I have allocated new space for my struct, can I just do a struct_allocator.construct() on it, or am I supposed to only do a stack_allocator.construct() on the stack element contained?

jens rasmussen wrote:

why one does not use assignment/placement new

jens rasmussen wrote:

I can't see how struct_allocator.construct() should be able to call stack_allocator.construct() - any comments?

led mike wrote:

real discussion about software development

Stuart Dootson wrote:

I work for company developing safety-critical software, so the management does actually care

George L. Jackson wrote:

Is that why you seem to go bananas after reading some of the posts on Code Project?

vector<char> buffer;
ifstream file;
size_t fileSize;

file.open( "..\\smime.p7b", ios::binary );
file.seekg( 0, ios_base::end );
fileSize = file.tellg();
buffer.resize( fileSize );
file.seekg( 0, ios_base::beg );

file.read( &buffer.front(), buffer.size() );

gleat wrote:

Why do you need this file loaded in a list<char> object instead of a vector<char>?

Stephen Hewitt wrote:

Using std::list like this is very inefficient;

Stephen Hewitt wrote:

You'd be better off using a std::vector.

Vector is the simplest of the STL container classes, and in many cases the most efficient.

<code>std::ifstream file (filename);
std::vector<char> vectorStore(std::istream_iterator<char>(file), std::istream_iterator<char>());
{or}
</code><code>std::list<char> listStore(std::istream_iterator<char>(file), std::istream_iterator<char>());</code>

      std::vector<char> fileContents;
      struct _stat stat;
      if (_stat(filename, &stat) == -1) throw std::runtime_error("Can\'t open " + file);
      fileContents.resize(stat.st_size);
      std::ifstream file(filename);
      std::copy(std::istream_iterator<char>(file), std::istream_iterator<char>(),
                fileContents.begin());

Stuart Dootson wrote:

strictly, you should be using unsigned chars,

Jeffrey Walton wrote:

file.open( "..//smime.p7b", std::ios::binary );

#include <bitset>

// Return a 12 bit set
std::bitset<12> BitsetWithNthBitSet(int n)
{
   return std::bitset<12>().set(n, true);
}

Stuart Dootson wrote:

std::bitset<12> BitsetWithNthBitSet(int n)
{
...