C / C++ / MFC

Tim Smith24-Dec-02 4:10

24-Dec-02 4:10

c1 = *s1;           
c2 = *s2;
if( __isascii(c1)  && isupper(c1) )
    c1 = islower(c1);
if( __isascii(c2)  && isupper(c2) )
    c2 = islower(c2);

That won't work as is. You should have tolower and not islower. Also, the other tests are redundant.

c1 = tolower (*s1);
c2 = tolower (*s2);

The docs in MSDN aren't totally correct. They say to use isascii and isupper, but that is only true for _tolower, not tolower. However, if you want to keep that code in there, then you can switch to using _tolower which is just a blind macro to add the proper value to convert the case.

Tim Smith

I'm going to patent thought. I have yet to see any prior art.

Nish Nishant24-Dec-02 4:20

Nish Nishant

24-Dec-02 4:20

Tim Smith wrote:

That won't work as is. You should have tolower and not islower. Also, the other tests are redundant.

WTF | :WTF:

That was a major GOOF-UP

Thanks Tim!!!!!

Nish

Author of the romantic comedy

Summer Love and Some more Cricket [New Win]

Review by Shog⁹
Click here for review[NW]

Scott H. Settlemier24-Dec-02 4:28

24-Dec-02 4:28

Converting both characters to lower case is wasteful though.
You can get better performance using a test like so:

const int uc='a'-'A';
bool bMatch=c==d || c+uc==d && c>='A' && c<='Z' || c==d+uc && d>='A' && d<='Z';

This usually short-circuits to three comparisons in the majority case of no match. Where this code is located, every bit counts..

Tim Smith24-Dec-02 4:45

24-Dec-02 4:45

Cute...

stricmp uses some assembler tricks to do the following:

if (c1 != c2)
{
   c1 = tolower (c1);
   c2 = tolower (c2);
   //test c1 c2 again
}

With the assebler tricks, it can avoid all the "jumps" associated with short cicuiting.

Tim Smith

I'm going to patent thought. I have yet to see any prior art.

Scott H. Settlemier24-Dec-02 4:51

24-Dec-02 4:51

yeah, there's something to be said for going back to
assembly at really crucial places. Just so long as it
is easy little jobs, it shouldn't make the whole too
unreadable.

Tim Smith24-Dec-02 5:06

24-Dec-02 5:06

Check my new post, the assembler version was slower than a stricmp version using your code. Smile | :)

Tim Smith

I'm going to patent thought. I have yet to see any prior art.

Tim Smith24-Dec-02 5:06

http://www.codeproject.com/string/#Regular%20Expressions

24-Dec-02 5:06

Very interesting...

I just made a stricmp with your clause and compared it to MS's __ascii_stricmp and your version won by around 25-30%.

Smile | :)

Tim Smith

I'm going to patent thought. I have yet to see any prior art.

Regular Expression?

Dov Sherman23-Dec-02 12:05

Dov Sherman

23-Dec-02 12:05

I'm doing some text parsing for a simple, scripted language and I'd like to use regular expression matching to check syntax. Is there any support for regular expression matching in MFC?

Re: Regular Expression?

C^hris L^osinger23-Dec-02 12:09

C^hris L^osinger

23-Dec-02 12:09

I'm not the droid you're looking for.

ThumbNailer

Re: Regular Expression?

Nemanja Trifunovic23-Dec-02 12:16

Nemanja Trifunovic

23-Dec-02 12:16

Dov Sherman wrote:
Is there any support for regular expression matching in MFC?

Yes if you use VC 7.

Beer | [beer]

Re: Regular Expression?

Todd Smith23-Dec-02 14:28

Todd Smith

23-Dec-02 14:28

boost.org has a regular expression class.

Todd Smith

Filling out other application dialogs

microcyb23-Dec-02 10:54

microcyb

23-Dec-02 10:54

O.K. need some directions on what to even call this function/call.

what I need to do is call another application, and fill out the fields with my application.

Part of an automation thing. In simple I wanted to call a simple .ini file, and have it use the information to fill out the dialog boxes in the other application.

could any one point me to what to search for or any links that could help in this process?

Note: NEWBEEE!!!!!!! Big Grin | :-D

Re: Filling out other application dialogs

mwilliamson23-Dec-02 11:37

Re: Filling out other application dialogs

23-Dec-02 11:37

You will to determine the window id of all the windows on the dialog you want to fill out and a handle to window you are filling out. Then simply use

::SetDlgItemText( hWnd, WindowId, "value" );

There was a password retival tool posted here, some of the code from it should help you to determine the window ids.

microcyb23-Dec-02 11:40

microcyb

23-Dec-02 11:40

Ahh I will continue to search, just had no clue what to search for.

would love to make it command lin based since it is to support at least 50 PC's.

Thanks for the direction!!!

PrintDlgEx, Visual C++ 6.0, and the Platform SDK

Jonathan Craig23-Dec-02 8:50

Jonathan Craig

23-Dec-02 8:50

I'm trying to use the PrintDlgEx method with Visual C++ 6.0. I have installed the Platform SDK (October 2002) and the include, lib, and exe directories for this are first in the directories option.

But I keep getting "error C2065: 'PRINTDLGEX' : undeclared identifier." It appears the complier is not look at the stuff in my "C:\Microsoft SDK" directories.

So what is required to get Visual C++ using the Platform SDK includes, libs, and exes?

Thanks for all input Wink | ;)

Jonathan Craig
www.mcw-tech.com

Re: PrintDlgEx, Visual C++ 6.0, and the Platform SDK

mwilliamson23-Dec-02 9:35

Re: PrintDlgEx, Visual C++ 6.0, and the Platform SDK

23-Dec-02 9:35

You must define _WIN_NT 0x500 in stdafx before you include the common dialog files. This means that your application will only run on windows 2000 / xp (which is when printdlgex as added).

Jonathan Craig23-Dec-02 10:15

Jonathan Craig

23-Dec-02 10:15

I don't see anywhere in the SDK include files a reference to _WIN_NT. I have added

#define _WIN32_WINNT 0x0500

and

#define WINVER 0x0500

to the stdafx.h file but I still get the same error.

Jonathan Craig
www.mcw-tech.com

Re: PrintDlgEx, Visual C++ 6.0, and the Platform SDK

mwilliamson23-Dec-02 11:13

Application Error only on some computers

23-Dec-02 11:13

Sorry, my mistake.

From CommDlg.h:

#if(WINVER >= 0x0500)
//
// PrintDlgEx structure.
//
typedef struct tagPDEXA {
DWORD lStructSize; // size of structure in bytes
HWND hwndOwner; // caller's window handle
HGLOBAL hDevMode; // handle to DevMode
HGLOBAL hDevNames; // handle to DevNames
HDC hDC; // printer DC/IC or NULL
DWORD Flags; // PD_ flags
DWORD Flags2; // reserved
DWORD ExclusionFlags; // items to exclude from driver pages
DWORD nPageRanges; // number of page ranges
DWORD nMaxPageRanges; // max number of page ranges
LPPRINTPAGERANGE lpPageRanges; // array of page ranges
DWORD nMinPage; // min page number
DWORD nMaxPage; // max page number
DWORD nCopies; // number of copies
HINSTANCE hInstance; // instance handle
LPCSTR lpPrintTemplateName; // template name for app specific area
LPUNKNOWN lpCallback; // app callback interface
DWORD nPropertyPages; // number of app property pages in lphPropertyPages
HPROPSHEETPAGE *lphPropertyPages; // array of app property page handles
DWORD nStartPage; // start page id
DWORD dwResultAction; // result action if S_OK is returned
} PRINTDLGEXA, *LPPRINTDLGEXA;
#endif

That means you need to define WINVER at 0x0500 before including Windows.h or CommDlg.h.

ElizabethC23-Dec-02 8:33

ElizabethC

23-Dec-02 8:33

I have Dell with Windows 2000; the application is a MFC EXE developed using Visual C++ 6.0 enterprise.

After applying some modifications to the application, some of my client computers are receiving "Application Error" message. But this does not appeariing in the development computer.

The client computers and the developer computer have the same model and RAM size.

I am very frustrated. The "Application Error" is very difficult to trouble shoot.

Eilzabeth

Scott H. Settlemier23-Dec-02 8:39

23-Dec-02 8:39

This sounds like a case for ....
CrashFinder[^]

Article here[^].

ElizabethC24-Dec-02 7:18

ElizabethC

24-Dec-02 7:18

I downloaded and installed CrashFinder with the CLW file dated 5/6/2002. I received compilation errors:

Compiling...
CrashFinderDoc.cpp
C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2065: 'SymDia' : undeclared identifier
C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2051: case expression not constant
Error executing cl.exe.

Do I have the good version?

Eilzabeth

Scott H. Settlemier24-Dec-02 12:57

24-Dec-02 12:57

That's a newer version. I think it must use an imagehelp.dll installed
with .Net or something. Try the older version available via the link in
the original article.

ElizabethC6-Jan-03 10:31

ElizabethC

6-Jan-03 10:31

The problem is solved. The problem was in the Oracle ODBC driver. The client has an older version of the driver. After I upgraded the driver to version 9. The error went away. The problem was from one of the CLOB fields. I think some data is "bad" in that field because other CLOB fields do not cause problems. Thank you all very much for help.

-Elizabeth

Eilzabeth

mwilliamson23-Dec-02 9:39