Hi All,
I am trying to generate a 32MB lookup table for log function by using Turbo C compiler. I call log function from library to calculate the corresponding values, and then write them to a file.The problem was when I read the whole table from the file in the end, only the first 98 items were correct while the rest of it were all wrong. Does anybody know what's wrong with it? and how to fix it?Many thanks indeed!
We have no way of knowing what is wrong with your code if you don't show us your code. The only obvious problem I can see from the limited information provided is that you're using a hopeless, obsolete compiler.
Code:while(!asleep) { sheep++; }
Given that TurbidCrap can only access 640KB of memory, 32MB is a long way off.
You fix it by getting a real compiler for your real OS. TC only works because of emulation magic.
These are good choices for example.
Free Developer Tools - Visual Studio 2010 Express | Microsoft Visual Studio
smorgasbordet - Pelles C
Code::Blocks
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
As a long time user of Turbo C, I feel well qualified to give you this opinion:
< Kiss it goodbye, and Upgrade >
I finally moved over in this last year (now using Pelles C for Windows), and although it takes some getting used to, it has capabilities that Turbo C could only dream about.
For Windows and C only (not Linux and not C++), but with 64 bit versions, and *FREE*, plus a small expert forum, it's a great choice, imo.
Thank you guys! Does Pelles C support for C++? How about borland C/C++ compiler?
I'd have gone with "Take it behind the barn and shoot it".Originally Posted by Adak
No. If you need C and C++ I'd suggest either MinGW, port of GCC to Windows, or Visual Studio Express if you have no aversions towards Microsoft. If you're on Windows, I'd go with VS Express. It's a good IDE, and it's free.
Disclaimer: This post shows my ignorance at the time of its making. I claim ownership of but not responsibility for all errors in it. Reference at your own peril.
