C / C++ / MFC

Socket Programming in MS. DOS

13-Feb-02 21:31

Whn you define this operator, the left hand parameter in the cat1 = cat2 expression is the object on which operator = is being called (that is, the object pointet to by this). A typical implementation of this operator goes like this:

CAT& CAT::operator=(const CAT& rhs)
{
  // copy all the members from the righthand side
  // to the left-hand object

  firstMember=rhs.firstMember;
  ...
  lastMember=rhs.lastMember;
  //return a reference to ourselves (note the *)
  return *this;
}

Seems a little cumbersome at first glance, but it is a pretty straightforward idiom once you get used to it.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Re: operators

Paul M Watt13-Feb-02 22:07

Paul M Watt

13-Feb-02 22:07

Operators in your custom classes are simply member functions of your class. The compiler just allows you to use syntactic sugar in order to invoke these functions.

Here is another way to look at it:

Rickard Andersson wrote:
CAT & CAT::operator=(const CAT & rhs)

CAT cat1;
CAT cat2;

cat1 = cat2;

This is the same as calling:

<br />
cat1.operator=(cat2);<br />

This is what it actually looks like to the compiler. This is also legal C++ syntax, so if your wanted to write your program using your custom class and this over loaded operator it would work. This goes for all operators for instance:

<br />
bool CAT::operator==(const CAT &rhs)<br />
{<br />
    return ...<br />
}<br />

could be invoked with this call:

<br />
if (cat1.operator==(cat2))<br />
{<br />
    ...<br />
}<br />

If you have any more questions feel free to ask.

Agus Kurniawan13-Feb-02 21:14

Agus Kurniawan

13-Feb-02 21:14

I have problem to implement Networking Application
using socket in MS.DOS because routine socket
this operating system isn't available. Cry | :((

Do I must install socket driver in order to implement
it in MS.DOS ? How to get it ? Confused | :confused:

Please Advise!!

Agus Kurniawan

Re: Socket Programming in MS. DOS

Joaquín M López Muñoz13-Feb-02 21:43

13-Feb-02 21:43

As you said, there's no native TCP/IP support in MS-DOS. A number of companies sell their own implementations of a TCP/IP library for MS-DOS (both for 16-bit apps and for 32-bit MS-DOS extenders). Do a search for "IP stack MS-DOS" on the net to get some links. Some of the libraries (like for instance WATTCP) are free.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

timer....!!!!

13-Feb-02 21:07

i want to simulate signal -- SIGALRM of ANSI C in to vc++
for that i m using settimer api but it not doing callback....plz help me out on this topic.......
code what i wrote is---->

#include <windows.h>
#include <stdio.h>
#include <conio.h>
UINT uResult;

VOID CALLBACK TimerAPCProc(
HWND hwnd, // handle to window for timer messages
UINT message, // WM_TIMER message
UINT idTimer, // timer identifier
DWORD dwTime) // current system time
{
printf("bharat");
getch();
}
int main(void)
{

uResult = SetTimer(0, // handle to main window
0, // timer identifier
10, // 10-second interval
(TIMERPROC) TimerAPCProc); // timer callback

if (uResult == 0)
{
printf("No timer is available.");
}

Sleep(20);
uResult=KillTimer(0,uResult);
if (uResult == 0)
{
printf("No timer is available.");
}

}

Joaquín M López Muñoz13-Feb-02 21:25

13-Feb-02 21:25

First of all, please next time tick on the "Display this message as-is (no HTML)" checkbox just below the edit area to make your code appear OK (otherwise <code'<'< code=""> characters mess with the HTML rendering.)

I'm afraid you cannot use <code>SetTimer for console programs. SetTimer needs a message processing pump in your thread to function properly, even if you don't specify any hWnd.
Al alternative approach goes through launching a separate thread that Sleeps the required amount of time and then invokes the callback function. It is likely that someone have wrote some code for that already, so maybe you should do a search on the net before start coding.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Tim Smith14-Feb-02 2:17

Tim Smith

14-Feb-02 2:17

Technically, you can use SetTimer in a console application. I do it all the time. You just need a message pump.

Tim Smith
Descartes Systems Sciences, Inc.

Joaquín M López Muñoz14-Feb-02 3:03

14-Feb-02 3:03

Technically, you can use SetTimer in a console application.

Of course.

I do it all the time

Do you? I'm curious as to know what kind of console apps you write with such a weird architecture. Do you mean your main thread falls into a GetMessage loop? If so, why do you choose console instead of a WinMain based solution?
No irony intended (really). I'm actually curious to know the reasons for devising this kind or architecture.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Tim Smith14-Feb-02 7:41

Tim Smith

14-Feb-02 7:41

Well, let me back track a little.

I have maybe used SetTimer once or twice in a console application. But, many times I have used SetTimer in a worker thread that doesn't have windows. Until recently, we didn't want to use waitable timers since they aren't supported under 95. Thus we just used the old SetTimer.

Tim Smith
Descartes Systems Sciences, Inc.

Joao Vaz13-Feb-02 23:14

Joao Vaz

13-Feb-02 23:14

You tried the SetWaitableTimer api?
It doesn't need a message pump.

Cheers,

Joao Vaz

Number of bitmaps in .bmp-file

Nemanja Trifunovic14-Feb-02 8:11

Nemanja Trifunovic

14-Feb-02 8:11

Take a look at this little article .

I vote pro drink Beer | [beer]

Onkie13-Feb-02 21:01

Onkie

13-Feb-02 21:01

Is there a way to determine how many separate bitmaps there are within a .bmp-file (e.g. one used for a toolbar). I like to find out the width and hight of every bitmap.

Thanks in advance,
Aart

Re: Number of bitmaps in .bmp-file

Paul M Watt13-Feb-02 21:15

Paul M Watt

13-Feb-02 21:15

Usually in a bitmap like this, all o fthe sub-bitmaps are the same size, so you could simply find out the width and the height of the bitmap in the header of the bmp file, then divide the smaller of the width and the height into the larger number, and that will tell you how many images are in the entire file.

Then the dimensions of the sub-images will be the smaller number for one dimension, and the larger number divided by the number of images in the file.

SDK!

George Clarence13-Feb-02 20:06

George Clarence

13-Feb-02 20:06

Hi Gurus!
Couuld you write me please the address, where I can download the SDK?

-George

Das war kein Heldenstueck, Octavio! Mad | :mad:

Re: SDK!

Jon Sagara13-Feb-02 20:05

Jon Sagara

13-Feb-02 20:05

http://www.microsoft.com/msdownload/platformsdk/sdkupdate

Jon Sagara

What about ?

Sonork ID: 100.9999 jonsagara

compiling in xp and dll errors on 2k

gus13-Feb-02 19:40

gus

13-Feb-02 19:40

I was compiling this app tonight in release mode...multithreaded, statically linked. os is xp using vis studio .net

I went to test it out on my 2k box and got a dll error referring to msvcr70d.dll, msvci70d.dll, and mcvcp70d.dll.

would the user 'need' to have these dll's installed(in which case it does work)? or is there another way around this?

Basically, I'm just looking to have one executable to hand out and not all the accompanying dll's. I was under the impression if i 'statically linked' it the exe would not be dependant on those. Why wouldn't i just use a 'dynamically linked' solution; keeping the exe size down even further and sending along the dll's anyway?

also, i do have the dll's on my xp system....I assume from when i installed vis studio and they're not on the 2k machine.

Any elaboration into my dilemma would be greatly..GREATLY appreciated.

thank you,
gus

Joaquín M López Muñoz13-Feb-02 20:02

13-Feb-02 20:02

Are you 100% sure you are statically linking your app? I mean, those DLLs look like C run-time library DLLs. I'd suggest you thoughoughly check your app is actually being statically linked. Also, if you have any other project without this problem you could check what its settings are and try to find the differences.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Michael Dunn13-Feb-02 20:18

Michael Dunn

13-Feb-02 20:18

You didn't test with the release version, but the debug version. The trailing d in the DLL names indicates they're the debug versions.

--Mike--
"There are only a limited number of jobs where they will ask to see the sausage. Most of them are in movies."
-- Christian Graus, 2/11/2002
My really out-of-date homepage
Sonork - 100.10414 AcidHelm
Big fan of Alyson Hannigan.

gus14-Feb-02 5:55

gus

14-Feb-02 5:55

thanks for the tip. I tried creating a new project config (because the one i was using was imported from vis studio 6) and then change to 'statically link'. compiled, ran it and the same thing. below is the config settings if that helps.

Name="Release|Win32"
OutputDirectory="Release"
IntermediateDirectory="Release"
ConfigurationType="1"
UseOfMFC="1"
CharacterSet="2">

Name="VCCLCompilerTool"
Optimization="2"
InlineFunctionExpansion="1"
OmitFramePointers="TRUE"
PreprocessorDefinitions="WIN32;_WINDOWS;NDEBUG"
StringPooling="TRUE"
MinimalRebuild="FALSE"
RuntimeLibrary="0"
EnableFunctionLevelLinking="TRUE"
TreatWChar_tAsBuiltInType="TRUE"
UsePrecompiledHeader="3"
WarningLevel="3"
Detect64BitPortabilityProblems="TRUE"
DebugInformationFormat="3"/>

Name="VCLinkerTool"
AdditionalDependencies="id3lib.lib"
LinkIncremental="1"
IgnoreDefaultLibraryNames=""
GenerateDebugInformation="TRUE"
SubSystem="2"
OptimizeReferences="2"
EnableCOMDATFolding="2"
TargetMachine="1"/>

Name="VCMIDLTool"
PreprocessorDefinitions="NDEBUG"
MkTypLibCompatible="FALSE"

Is there one or more specific settings i should check to make sure it's statically linked? I'm using mfc and have that setting statically linked. I'm not sure of what others i would have to check. any ideas?

thanks again,
Eric