Oops... I forgot to look at the date! Someone linked me to this thread from one of mine!
Sorry guys!
Type: Posts; User: Bladactania
Oops... I forgot to look at the date! Someone linked me to this thread from one of mine!
Sorry guys!
But after looking at DOSBox, I'll try that first
Given the fact that he has programmed in Visual Basic, learning to use the Visual C++ IDE will be a snap.
I was considering simply installing XP as well as Vista 64-bit so I could boot to either...
Hello all,
I've writing software to run on an SBC running DOS 6.2. I've been using Borland Turbo C 3.0 compiler. I've just got a new laptop with Vista, and the Borland compiler will not run on it....
Yeah that's what I originally tried (inport). I've never written inline assembler functions before... always fun to learn something new :)
asm?
I tried using inp(), inpw(), inport(), and inportb().
I get an undefined error for inportw()
char line[BUFSIZ]; // Creates a character array BUFSIZE characters long
double fPurchase_Amount = 0.0; // Creates a float variable and initializes to 0.0
fgets(line, sizeof(line)-1, stdin); //...
I just had to say that I loved the "shooting yourself in the foot" analogy :)
Greetings all... (I'm using Borland Turbo C/C++ 3.0)
I am using an ADC board (See Getting Started Sheet) attached to an SBC running DOS 6.2. There is only a sparse and seemingly rough...
if (isalpha(str1[i]))
{
printf("\n%c", str1[i]);
}
else
{
printf("\n%c", str1[i]);
}
Instead of NULL, would setting the prt to 0 work?
I seem to remember seeing somewhere that you cannot allocate memory for a pointer that is already set to NULL. Is this true?
It was a timing issue I was worried about. There was a chance that the way I had structured my main loop, that I might be freeing a variable that might not have been malloced during the iteration.
...
Will it cause problems if I call free() on a char* that I never called malloc() for?
Look in the Installation Directory. For me it's c:\program files\MS Visual Studio 8\VC\include
It would be helpful to see what the compiler errors you get.
I do know that the brackets '[]' in your function declarations in the parameters are not necessary, but I'm not sure if they would...
Your compiler should have an include folder somewhere that has all the header files in it.
I don't understand the need for making a copy of "p" Couldn't it be returned by value then incremented?
There's no explanation about WHY that makes a difference in a for loop.
Because the function is designed to accept any integer pointer, not only the one inside the structure.
Yes you can do that, but you are likely to get a seg fault or other unexpected behavior if you do something like that.
Just because something works SOMETIMES doesn't mean it will work ALL times.
the add(as); in the original post is results in the same thing as the same line in your code. In the original, he passes a pointer to the structure, so any changes to as within the function are...