From: Martin Str|mberg Subject: Re: turbo c++ vs djgpp Newsgroups: comp.os.msdos.djgpp References: <54527c66 DOT 0207290812 DOT 11eba9ab AT posting DOT google DOT com> User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (NetBSD/1.5_BETA (alpha)) Message-ID: <1027977284.571150@queeg.ludd.luth.se> Cache-Post-Path: queeg.ludd.luth.se!unknown AT speedy DOT ludd DOT luth DOT se X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/) Date: 29 Jul 2002 21:14:44 GMT Lines: 27 NNTP-Posting-Date: 29 Jul 2002 21:14:44 GMT NNTP-Posting-Host: queeg.ludd.luth.se X-Trace: 1027977284 news.luth.se 442 130.240.16.109 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com pandu wrote: : I found some problems in using functions/methods of iostream.h and : fstream.h . : I have written a program in Turbo C++, and when it was compiled (by : DJGPP) , there were some error massages that concerned stream (like : cout, cin, fout,fin, etc). : Would you tell me how to solve these problems ? How could we? You don't show us the error messages! But if it's gpp 3. you're using, then your C++ probably isn't current standard C++. : If we operate a big multidimensional array, is it necessary to use a : pointer and memory allocation (malloc or calloc) ? On the stack, yes. The stack is limited. Global ones, no. : Are there any other ' differences' between Turbo C++ and DJGPP ? Well, with DJGPP you have the source and very much more up-to-date C++. Right, MartinS