Re: C program to extract values from EXCEL file - C / C++ / MFC Discussion Boards

CPallini31-Jan-12 2:39

31-Jan-12 2:39

strtod (that is the 'standard' C++ strtod, I never heard about StrToD) is not 'strange': it is a function satisfying its own requirements that are clearly explained, for instance here[^]. If it doesn't fit your needs, then, well, the right way is to write your own one (as you did).

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: strange realization of StrToD()

a_matseevsky31-Jan-12 3:37

a_matseevsky

31-Jan-12 3:37

You are right about lowercase: strtod(const char *nptr, char **endptr) returns floating point value and a pointer to the first char, that stops scanning. It means, that if I have for example such string "12.3 0.07" and give pointer to this string to strtod for eating, it will return me 12.3 and pointer to the next char after '3'. Thats all right, no objections. But name me one reason to scan THE WHOLE string??? Why do not stop scanning after four first chars? It is my non-humble opinion: it typical left-hand approach.

Re: strange realization of StrToD()

C^hris L^osinger31-Jan-12 4:04

C^hris L^osinger

31-Jan-12 4:04

strtod uses strlen, internally - at least in VS2008.

but VS2010 fixes this, reportedly.

image processing toolkits | batch image processing

Re: strange realization of StrToD()

a_matseevsky31-Jan-12 6:10

a_matseevsky

31-Jan-12 6:10

I use VS2005. I like it and this example of strange behavior is the only one what I actually met. No matter, build-in assembler lets me write compact and efficient procedures, when and if I have need in extra performance.

Re: strange realization of StrToD()

JackDingler31-Jan-12 11:54

JackDingler

31-Jan-12 11:54

Looks like you found a bug.

Re: strange realization of StrToD()

a_matseevsky31-Jan-12 12:32

a_matseevsky

31-Jan-12 12:32

I wouldn't say so: procedure works correctly. It is only inefficient realization, no more. I met a real bug in VS 6.0, but now it is of no use to speak about such ancient soft. Sometimes VS2005 asks me for confirmation, when I try to close prog, currently running under debugger, but it happens probably due to old age of my particulat exemplar.

C program to extract values from EXCEL file

Faez Shingeri31-Jan-12 1:46

Faez Shingeri

31-Jan-12 1:46

Hi,

Can we write a C program to get a particular column values from an EXCEL file and use them as input for another file.
Eg: I want to retrieve all the values of the 3rd column of an excel file and then use that value for searching in another text file and finally replacing it with "xyz".

Thanks,
Faez

Re: C program to extract values from EXCEL file

CPallini31-Jan-12 2:35

CPallini

31-Jan-12 2:35

Yes, we can.
You may have a look at one of the many articles about Excel automation[^] here at CodeProject.
They are mainly focused on C++ language however.
In fact the bad news of your task are that you have to call COM from C (feasible but bit involuted).

Re: C program to extract values from EXCEL file

Faez Shingeri31-Jan-12 17:33

Faez Shingeri

31-Jan-12 17:33

I read the article regarding Excel automation and COM but could not find anything about extraction of values from a particular column of an Excel file.

I am using Eclipse IDE and gotta write a C code to open an Excel file and extract its fourth and fifth column values.

Any kinda help would be appreciated.

Thanks,
Faez

Re: C program to extract values from EXCEL file

CPallini31-Jan-12 21:44

CPallini

31-Jan-12 21:44

There are some examples on how to access cells, for instance via ADO: "How to Read and Write Excel Files in C++ via ADO"[^] or directly parsing the Excel file: "BasicExcel - A Class to Read and Write to Microsoft Excel"[^]

BTW I've balanced the pointless downvote.

Re: C program to extract values from EXCEL file

Faez Shingeri31-Jan-12 22:51

Faez Shingeri

31-Jan-12 22:51

The below link helped me..

http://www.libxl.com

But now am facing other different problem

http://www.codeproject.com/Messages/4144507/Re-Undefined-reference-error-while-using-libxl-lib.aspx

Thanks for help

firmware coding in C

Ebe7230-Jan-12 23:16

Ebe72

30-Jan-12 23:16

Need help to understand this line of code
step = (struct MyStep*)BigStep
given,
typedef struct MyStep {...structure definition...};
const struct MyStep BigStep[]{...an array of MyStep...};

Thank you

Re: firmware coding in C

Richard MacCutchan30-Jan-12 23:37

Richard MacCutchan

30-Jan-12 23:37

I don't know what version of C/C++ that is but it looks wrong to me. Why not show the exact code that you are trying to understand?

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman

Re: firmware coding in C

CPallini31-Jan-12 2:25

CPallini

31-Jan-12 2:25

That:

Takes BigStep (the address of the array of const MyStep structs).
Casts it to struct Mystep * (hence discarding the const constraint).
Assigns the result to step (that is probably defined as struct MyStep *).

Re: firmware coding in C

Bram van Kampen31-Jan-12 12:27

Bram van Kampen

31-Jan-12 12:27

Hi,

Ebe72 wrote:
step = (struct MyStep*)BigStep
given,
typedef struct MyStep {...structure
definition...};
const struct MyStep BigStep[]{...an array of MyStep...};

Sorry, but by itself, this is Absolutely Meaningless. Firmware, Hardware, or Software Coding, makes no Real difference. It is something written in 'C'.
Question 1. Does your Code Compile.
If it does, you're lucky!
Question 2.
Does your code do what it is supposed to do.
If the answer is 'Yes' set a number of breakpoints around where the structure is used, and that will soon tell you (May take some patience) what happens, and what's what.

If your code does not Compile, you probably left out a Header. If it compiles, but does not link, you left out Library References.

If it Compiles and Links, but does not do what you expect, go back to the Docks and find out what it was supposed to do in the First Place!

Set Breakpoints, and find out what's going on.

This is a process called 'Debugging' It takes Time Skill and cunning, and the gray cells of 'Hercule Poirot'. It cannot be thaught as such, but you get experienced with your best friend, your Compiler.
Famous Chestnuts:-

<br />
if(x=0){...Do Something...} (Never Happens)<br />
<br />
int x==1;<br />
<br />
for(x=0;x=10;x++){...Do Something...}<br />
switch(){// In VC5 Trashes the Compiler<br />
break;<br />
}<br />

Hope this helps, if not, we need to see a little bit more than two lines of code, part of a Structure Definition. We are Not mindreaders Smile | :)

Bram van Kampen

Re: firmware coding in C

Erudite_Eric31-Jan-12 21:05

Erudite_Eric

31-Jan-12 21:05

BigStep[] is an array of MyStep structures. BigStep is a pointer to that array, iem the address of the first storage hole. ie, &BigStep[0].

'step as (MyStpe*)BigStep' points another pointer, this one a non const I assume (depending on how 'step' is declared), to the same address.

(BTW with the typedef you dont need to use ctruct MyStep* as the cast, MyStep* alone will compile since it is a new defined type.)

==============================

Nothing to say.

::ifstream.open behaves differently in VC6 and VS2010

KASR130-Jan-12 22:31

KASR1

30-Jan-12 22:31

In VC6 when we use ::ifstream.open("test.txt") call creates a file if the specified file is not found in the location. But in VS2010 it does not create a file when its not found. Why is this differece and how to resolve this problem?

Re: ::ifstream.open behaves differently in VC6 and VS2010

CPallini30-Jan-12 22:42

CPallini

30-Jan-12 22:42

It looks VS2010 is more 'compliant' (see ifstream::open[^]).
It doesn't look a problem to me, however you may provide the second argument with the open mode you wish, if you need.

Re: ::ifstream.open behaves differently in VC6 and VS2010

KASR131-Jan-12 3:24

KASR1

31-Jan-12 3:24

i m wonderring which second argument option will work like as vc6.

Re: ::ifstream.open behaves differently in VC6 and VS2010

Albert Holguin31-Jan-12 3:37

Albert Holguin

31-Jan-12 3:37

Try them out to see which one works as desired... do you really need people to do all the thinking for you?

if the default is ios_base::in (see parameters):

void open ( const char * filename, ios_base :openmode mode = ios_base::in );

then just try making it ios_base::out (if you're only writing to it, or in/out if you're reading and writing).

open(filename, ios_base::out);
//Or maybe
open(filename, ios_base::in | ios_base::out);

Re: ::ifstream.open behaves differently in VC6 and VS2010

KASR131-Jan-12 3:42

KASR1

31-Jan-12 3:42

Even i tried all this and posted here when things are not working.
None of the above options creates a file when its not found. only VC6 open does.

Re: ::ifstream.open behaves differently in VC6 and VS2010

Albert Holguin31-Jan-12 5:17

Albert Holguin

31-Jan-12 5:17

if you're using the ifstream version, it sort of implies that you're pulling in data (thus, why would you want to create a file if it doesn't exist)... did you try to fstream/ofstream version of open? did you try putting in the whole path to the file to see if that made a difference?

Basic debugging... come on...

Re: ::ifstream.open behaves differently in VC6 and VS2010

KASR11-Feb-12 7:29

KASR1

1-Feb-12 7:29

finally i confirmed that vc6 ifstream::open has bug and this has been fixed in vs2010. So i modified the code to match with existing behaviour.

basic Winsock / IOCP / UDP question

SledgeHammer0130-Jan-12 13:01

SledgeHammer01

30-Jan-12 13:01

I wrote a scalable TCP server using I/O completion ports. The basic design is that I kick off an accept thread that waits forever for the FD_ACCEPT network event and then accepts the connection and ties it to the I/O completion port. There are 4 to 8 worker threads that process events coming off the I/O completion port. Everything works great.

Now I'm trying to add scalable UDP support. I am new to UDP, so I'm not sure how I should go about this.

1) if I have 4 to 8 worker threads to process TCP events coming off the I/O completion ports, should I do the same for UDP? Some links I found said you only need one thread for UDP and there is no need for IOCPs??? This seems wrong as say I get 1000 UDP events at the same time, I'd like to be able to multi-thread process them.

2) I don't seem to get any network events when a UDP client "connects", just get the FD_OOB at "start up".

Was kind of expecting this to behave like the TCP side in which I'd get a network event when the client "connects" and then another event when there is data to read (via WSAEnumNetworkEvents())...

I know UDP is connectionless, but I'm not getting any network events when the server gets data.

Re: basic Winsock / IOCP / UDP question

Jochen Arndt30-Jan-12 22:19

Jochen Arndt

30-Jan-12 22:19

UDP is connectionless, so you did not get a connect event. But you can get events when data arrives. Using one receiving thread is enough even with many clients when the UDP packets are small. A typical implementation would be:

C++

m_hevWSA = ::WSACreateEvent();
m_sockRecv = ::WSASocket(AF_INET, SOCK_DGRAM, IPPROTO_UDP, NULL, 0, WSA_FLAG_OVERLAPPED);
::bind(m_sockRecv, reinterpret_cast<sockaddr*>(&sinRecv), sizeof(struct sockaddr));

// Worker thread
UINT CMyClass::WorkerThread(void)
{
    int nRet = -1;
    bool bPending = false;
    DWORD dwWSARead = 0;
    DWORD dwWSAFlags = 0;receive flags
    char NetBuf[DGRAM_BUF_SIZE];
    WSABUF WSABuf = { DGRAM_BUF_SIZE, NetBuf };
    HANDLE ahWait[2] = { m_evKill.m_hObject, m_hevWSA };
    WSAOVERLAPPED ovWSA;
    struct sockaddr_in SenderAddr;
    ::ZeroMemory(&SenderAddr, sizeof(SenderAddr));
    ::ZeroMemory(&ovWSA, sizeof(WSAOVERLAPPED));
    ovWSA.hEvent = m_hevWSA;
    do
    {
        int nWSAErr = 0;
        unsigned nNetRead = 0;
        if (!bPending)
        {
            dwWSARead = 0;
            dwWSAFlags = 0;
            WSABuf.len = DGRAM_BUF_SIZE;
            WSABuf.buf = NetBuf;
            int nSenderAddrSize = sizeof(SenderAddr);
            if (::WSARecvFrom(m_sockRecv, &WSABuf, 1, &dwWSARead, &dwWSAFlags,
                (SOCKADDR *)&SenderAddr, &nSenderAddrSize, &ovWSA, NULL) == 0)
            {
                nNetRead = static_cast<unsigned>(dwWSARead);
            }
            else
            {
                nWSAErr = ::WSAGetLastError();
                if (nWSAErr == WSA_IO_PENDING)
                    bPending = true;
                else
                    nRet = 1;
            }
        } // if (!m_bPending)
        switch (::WaitForMultipleObjects(bPending ? 2 : 1,
            ahWait, FALSE, bPending ? INFINITE : 0))			
        {
        case WAIT_OBJECT_0 : nRet = 0; break;
        case WAIT_OBJECT_0 + 1 :
            if (::WSAGetOverlappedResult(m_sockRecv, &ovWSA, &dwWSARead, FALSE, &dwWSAFlags))
            {
                nNetRead += static_cast<unsigned>(dwWSARead);
                bPending = false;
            }
            else
            {
                nWSAErr = ::WSAGetLastError();
                if (nWSAErr != WSA_IO_INCOMPLETE)
                    bPending = false;
            }
            ::ResetEvent(m_hevWSA);
            break;
        }
        if (nNetRead)
        {
            // process data
        }
    }
    while (nRet == -1);
    return (nRet == STILL_ACTIVE) ? 1 : static_cast<UINT>(nRet);
}

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.