I am getting "class not registered" errors on CoCreateInstance even though
the service is up and running on my machine, and I have the Platform SDK
(ergo, "Imapi.h" where the CLSIDs are defined.)
'lil help?
WTH
1. Has anyone ever seen this before? - CSharp/C#
2. anyone ever post to Perl newsgroups?
just curious, cause i have to say, i have never met with a bigger bunch of snobs. look, i know i am not the most "polite poster" but have been posting to this newsgroup for years. and no matter how stupid my question is, someone answers it here. and i have answered some stupid ones myself. but i always came out of this newsgroup knowing that "anyone" could get help here. over there, i get flack for repeatedly using PERL instead of Perl...and the likes....i mean wow...i was just curious, "am i that bad? (which to a point i am, i acknowledge that) or is it them as well?" thanks
4. Has anyone ever... (was: Exception handling)
This comment from jeffc sparked a thought:
> The assert doesn't do anything in a release build, and that
> is its advantage, you can afford to put more tests into your
> code then you ever would if the tests were to be exercised
> in release versions.
>
> Would we ever put a check for validity into every method of
> our Point class if it were to be exercised in customer
> builds? Of course not, the test will be exercised millions
> of times
> ...
Error checking (and recovery) in itself isn't a bad thing in
a release build - it's the cost that people object to. A really
clever compiler could potentially take care of this problem -
for example:
T& Array::operator [] (int index)
{
assert(index >= 0 && index < arrayLength);
return arrayVal[index];
}
void incrementValues(Array &a)
{
for (int n = 0;n < a.length();++n)
{
++a[n];
}
}
An intelligent compiler could recognise that in this particular
loop, the assert condition is always false, and so the check is
not necessary at run time.
Has anyone ever seen an optimising compiler that actually does
this ?
This would require:
- data flow analysis across function boundaries
- some way of preventing execution of the "assert" code:
- multiple entry points to functions with preconditions ?
- multiple versions of functions, with and without checks ?
(similar to the code generation done by templates)
(but avoid having 2^N versions of a function with N asserts !)
- possibly embedding this information in object modules / libraries
so separate compilation is handled, too
This applies to "optimising out" any block of code the compiler
knows will never be entered, not just asserts like this one.
David F
5. anyone ever take ikmnet test for visual C++ 6
6. Did anyone ever use the VTK in BCB?
7. Slightly OT: Visual Studio formatting of get/set methods - CSharp/C#
8. Slightly OT: Installing applications
If I build an .exe file in VS C# 2008 Express, I can copy this executable to another PC, and if I double-click on it, the programme runs fine. What are the advantages + circumstances where I should install a programme that I write (eg like Adobe Reader is installed) rather than simply copying the .exe file?