Recent content by CodingNovice

i think that should be (!str || !*str) first you check the pointer isnt null then you check the strings first byte isnt 0.

shouldnt that be :- static void* operator new(size_t size, char const* file, int line) and static void operator delete(void* memaddr,size_t size,char const* file,int line) Also in his book effective c++ I believe scott meyers suggests checking the size of the object passed to your operator...

There are safe versions about but they operate slower. The basic rationale was that locking is expensive and if you dont need it why pay for it. Its not hard to write a class with a container member and a critical section to sync access to the container. In general where stl containers must be...

If you read chapter 1 you will see this.... template<template<class Created>class CreationPolicy> class WidgetManager:public CreationPolicy<Widget> { ... } I think this says it all really. If you stare at it long enough and reread it a couple of times it will all click into place.

The bootloader will have to be in asm. The kernel is most likely going to be written in a mixture of C and asm. The runtime library will be written in C and possibly asm. The shell especially if graphical is probably going to be in C++, but you can use C. Read Tanenbaums book.

as windows will not give you direct access to the hardware then the answer is no. You can use the GDI to do what you want by making a bitmap from your int array and using BitBlt() to blit it. Draw on a memory DC then blit the memory DC to the screen DC to reduce flickering.

a full shop stock control,contacts and invoicing system written generically so you can tailor it to individual companies using nothing more than a configuration applet or ini files. try to build in printing and generation of invoices and credit notes, stock control,email generation,sorts and...

Its called return by value. If the function returned a wstring& then that would have been illegal as the wstring being referenced would have been destroyed before the reference was used. But to return an object by value is perfectly feasible tho a little expensive.

if each process is nicely self contained and can talk using the usual forms of IPC where necessary then that is probably the better solution.

I know gdi+ can do bmp to jpeg and jpeg to bmp. Im not sure if it supports TIFF out the box but might be worth a look. The Image class has some functions to help with conversions.

Im sure localtime can do it as well but I dont know anything about C locales.

yeah simple if you know the time difference just add it to the hour member of the struct. i.e. gmt to cet #include <stdio.h> #include <time.h> #define CET (1) int main () { time_t rawtime; tm * ptm; time ( &rawtime ); ptm = gmtime ( &rawtime ); printf ("CET now is :-%2d:%02d\n"...

They are access violations caused simply by overwriting the bounds of your array.The exception isnt writing to the memory, you are, thats what causes an exception to be raised. Thats obviously how your compiler/debugger deals with this.

or perhaps std::string ??

use strncpy and strncat.