 |
|
|
Veni, vidi, ristagnavi
|
|
|
|
|
|
|
Veni, vidi, supersedi.
Veni, vidi, vici.
|
|
|
|
|
|
|
i think this belongs in the Hall Of Shame
|
|
|
|
|
|
|
// not code
void lxt971reset()
{
int temp2,temp1;
pioreset1=pioreset1 | 0x0010;
// hex 10 = binary 10000; | is Bitwise OR; sets the 5th position from the right in pioreset1 to a
one. Probably turning on some kind of switch
*pioaddr_ptr=9<<24;
// Not sure why one would do this but this shifts 9 (binary 1001) 24 bits to the left ( also multiplies 9 times (2 to the 24th power) which equals Binary 10010000000000000000000000000 and stores it
*piowrdata_ptr=pioreset1;
// sets a pointer to the value from setp 1
wait(10);
// I geuss a delay to let the previous action to take effect
*piowr=1;
// Turn something on
*piowr=0;
// Turn it off
wait(1000);
// Another delay
pioreset1=pioreset1 & (~0x0010);
// (~0x0010) = 01111 bacically the complement of 10000 from step 1 "piorset1 & 01111" turns off the switch truned on in step 1
*pioaddr_ptr=9<<24;
// Same as step 2 but with switch off
*piowrdata_ptr=pioreset1;
// Same as step 3
wait(10);
// more delay for timing I suppose
*piowr=1;
*piowr=0;
// The old On/Off again
}
// never did use temp1 or temp 2;
John Nawrocki
Chief Technical Advisor
Custom Molded Products
|
|
|
|
|
|
|
Needs formatting!
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
|
But you missed to mention your postal address.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
|
|
Using Microsoft's NMAKE with -I option for include paths. It works for the include files in these folders, but can't seem to find one in a named subfolder:
Here's the resulting command & error message:
cl /nologo /Ox /MD /EHsc /W3 /D_CRT_SECURE_NO_DEPRECATE -I "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys"; -I. "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys" "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include" "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include" -DAVOID_WIN32_FILEIO -DCHECK_JPEG_YCBCR_SUBSAMPLING -DDEFAULT_EXTRASAMPLE_AS_ALPHA -DSTRIPCHOP_DEFAULT=TIFF_STRIPCHOP -DSTRIP_SIZE_DEFAULT=8192 -DLOGLUV_SUPPORT -DNEXT_SUPPORT -DTHUNDER_SUPPORT -DLZW_SUPPORT -DPACKBITS_SUPPORT -DCCITT_SUPPORT -DTIF_PLATFORM_CONSOLE -DFILLODER_LSB2MSB /c tif_unix.c tif_unix.c tif_unix.c(35) : fatal error C1083: Cannot open include file: 'sys/types.h': No such file or directory
Two things to note:
1. The "missing" file, "types.h", IS in the "sys" subfolder of one of the include paths, so "sys/types.h" should have been found, and
2. The "sys" subfolder was also included (out of desperation) and types.h STILL wasn't found.
Any ideas why this include file can't be found?
"Microsoft -- Adding unnecessary complexity to your work since 1987!"
modified 24 Feb '12.
|
|
|
|
|
|
|
I haven't messed with make files in a very long time, but it seems that the preprocessor is going to look in the following folders for sys/types.h:
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys"
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys"
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include"
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include" Of the above, only the last one would appear to contain a folder named sys, correct?
Does the \ vs. / make any difference? I don't think it does, but I just wanted to mention it.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
|
|
Thanks for the info, but the problem turned out to be something else.
"Microsoft -- Adding unnecessary complexity to your work since 1987!"
|
|
|
|
|
|
|
I suspected it was after reading Richard's post.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
|
|
Isn't sys/types.h a POSIX include file? Can you use it on Windows (I mean without Cygwin)?
Veni, vidi, vici.
|
|
|
|
|
|
|
I just checked - it is in the Windows sys directory.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
|
If we break this command into its constituent parts we get the following:
cl /nologo
/Ox
/MD
/EHsc
/W3
/D_CRT_SECURE_NO_DEPRECATE
-I "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys";
-I.
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys"
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include"
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include"
-DAVOID_WIN32_FILEIO
-DCHECK_JPEG_YCBCR_SUBSAMPLING
-DDEFAULT_EXTRASAMPLE_AS_ALPHA
-DSTRIPCHOP_DEFAULT=TIFF_STRIPCHOP
-DSTRIP_SIZE_DEFAULT=8192
-DLOGLUV_SUPPORT
-DNEXT_SUPPORT
-DTHUNDER_SUPPORT
-DLZW_SUPPORT
-DPACKBITS_SUPPORT
-DCCITT_SUPPORT
-DTIF_PLATFORM_CONSOLE
-DFILLODER_LSB2MSB
/c
tif_unix.c
tif_unix.c
tif_unix.c
(35) : fatal error C1083: Cannot open include file: 'sys/types.h': No such file or directory
The only directories included by the -I option are "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys" and . (dot). All the other directory names seem to be orphaned in the command line. I'm also not sure why "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\sys" has that semi-colon character after it. I think you need to check your NMAKE source file.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
|
You nailed it Richard! That was the problem! Many thanks (and 5 points)!
"Microsoft -- Adding unnecessary complexity to your work since 1987!"
|
|
|
|
|
|
|
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
|
Maybe it's a copy/paste bug but that command line doesn't look right to me.
1. The second include is given with option "-I.", that dot doesn't belong there.
2. The rest of the include paths are given without -I arg so the compiler probably won't know what to do with those.
|
|
|
|
|
|
|
1. That just means add the current directory to the include path(s).
2. I already noted this in my comment above.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
|
1. Yes that could be the intention, but the compiler would look there in any case, wouldn't it?
2. So then we know it took me more than 36 minutes to type in that comment. No wonder I'm not a regular...
|
|
|
|
|
|
|
1. Not all compilers do that automatically. As far as I recall some flavours of UNIX require this.
2. Apologies, I did not check the time differences.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
|
1. Oh absolutely,
2. you were right, though.
|
|
|
|
|
|
|
That was the problem (as Richard also pointed out). Thanks and 5 points!
"Microsoft -- Adding unnecessary complexity to your work since 1987!"
|
|
|
|
|
|
|
Is it safe to pass CComVariant declared locally to other function
1. Can I pass the CommVariant to other function, when not created using new ?
2. Should I free it/delete expecitly some where ?
3. Is it safe ? any precauions ?
CComVariant comVart;
comVariant.vt = VT_I4;
comVariant.intVal = 10;
SendComVariantToOtherFunction(comVart);
Thanks in advance!!
|
|
|
|
|
|
|
ptr_Electron wrote: 1. Can I pass the CommVariant to other function, when not created using new ?
Yes.
ptr_Electron wrote: 2. Should I free it/delete expecitly some where ?
No, when not allocated on the heap. When using new, it must be of course freed using delete. Everything else is done by the destructor.
ptr_Electron wrote: 3. Is it safe ? any precauions ?
It is safe. But you must take care when assigning data (type and data must match).
|
|
|
|
|
|
|
I want ot check CComVariant.boolval is valid and extract bool value from it
if(SUCCEEDED(m_abc->GetProperty("test", comVar)))
{
if (comVar.boolVal == VARIANT_TRUE)
{
}
}
please help!
|
|
|
|
|
|
|
It could be that m_abc->GetProperty returns something other than a bool, so you should also check comVar.vt to see that you really have a boolean.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Rant 
Admin