| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12
Comments:
<0> yup
<1> I'm working at a program, that uses WTL 7.1
<1> does any one know how to work with WTL ?
<0> ms hooked us up with some nice beer last time
<2> it's full, so doesn't look like i'll make it anyway
<0> ugh, ****s
<2> if you win the xbox 360, shoot it my way
<0> haha word
<1> I'm using visual c++ 2003
<1> and the program works fine
<1> I've installed WTL 7.5 and
<2> the event went out on my company's mailing list, so i bet we took all the spots
<3> -_XXXXX_- VERSION mIRC v6.12 Khaled Mardam-Bey
<3> lol
<3> What a wannabee root
<1> the 32bit color toolbar doesn't look ok
<4> lol
<1> does anyone listen ?
<5> WTL? is it still supported?
<2> int64, sorry i haven't used WTL since it was an internal pet project
<1> ha
<0> ya same here
<1> yes
<1> is still used
<0> err, I thought you worked for ms
<1> is an alternative to MFC
<1> no. I don't work for ms
<0> not you :P
<2> me?
<2> not since i moved back to virginia
<1> :)
<0> ya
<0> ahh good deal
<1> anyway, I will come back later...:)
<4> is cin>> reading only one word ?
<3> That isn't a function.
<5> until first space character encountered
<3> You mean operator>>(std::string const&, std::string const&);
<6> there's a >> for two strings?
<3> and that stops reading at a space by default.
<6> Run, what is that supposed to do?
<3> I meant...
<3> You mean operator>>(std::istream const&, std::string const&);
<3> sorry
<6> ah
<3> I never use operator>>, I hate it.
<7> melfar actually until whitespace
<8> can someone please explain me what the hell are namespaces?
<3> Do you hate someone too?
<8> i've been using C and some old C++ and now under .NET i have this ****ty namespaces
<8> i hate namespaces
<8> :D
<7> they're used to keep names from colliding
<3> I suppose you understand the concept of namespace collisions?
<9> okay, so if i got like 3-4 cl***es each one with a .h and .cpp,
<9> how can I acces each other in a main prog using namespaces
<3> Autor X writes libx, author Y writes liby. Both use 'foobar' as global variable - then person Z wants to use both libx and liby... oops.
<7> that's orthogonal to namespaces
<9> i mean, under win32 projects it's a simple #include
<3> Solution: all global functions and variables need to be unique.
<7> what's a simple #include?
<10> what include files do i need so that i can use the CFileDialog common dialog?
<3> Therefore, people need to write loooooong names.
<3> And they hate that, thats why they invented namespaces.
<3> So, instead of having to write libx_foobar all the time - the author of libx adds namespace libx { } around his code, and just writes foobar.
<9> mkay, that makes sense, still i got problems seeing all the functions
<11> valian: it's part of MFC
<7> all what functions
<3> [KONQUEROR]: You can access foobar inside namespace libx { }, outside that namespace as: libx::foobar
<10> when i try to declare instance of CFileDialog it says undeclared identifier
<9> okay, now what does using namespace mean?
<3> or, if you have to type it very often too, and there is no collision, you can write/add: using libx::foobar;
<9> outside i use libx::foobar
<3> and the every following 'foobar' will refer to libx::foobar
<9> aha
<9> finally, i got stuck in using namespace and ::
<9> :D thankx
<10> CFileDialog ldFile(TRUE);
<10> undeclared identifier?
<12> [KONQUEROR] : in the future, understand something before you hate it
<9> i still hate it
<3> "using namespace libx" is killing a mosquito with a shotgun, or something like that... it's nice if it works (still not collisions) but normal would be that you immediately get collisions: you kill the whole namespace idea.
<9> okay, now it says: comPort: a namespace with this name does not exist
<5> [KONQUEROR]: do you by any chance feel yourself being watched either?
<3> [KONQUEROR]: no 'namespace', just: using libx::foobar;
<9> ahh,
<9> but why is it then using namespace System; ?
<3> because System is a namespace
<9> now it says symbol cannot be used in a using-declaration
<10> what is mfc and how to use it
<9> yes, but comPort is a namespace too, itsn't it? i declared like that
<3> [KONQUEROR]: time to show to code then
<11> GetOpenFileName() does the same as CFileDialog
<13> Question
<13> I dont remember, whats the default namespace?
<5> ::
<14> mfc is a cl*** lib (pretty damn awful)
<13> i.e. if for some reason you coded in orig namespace, then 'using System;' , how would you refer to the orig?
<5> pretty damn unsupported
<13> just ::?
<3> [l: Nah - if you write "using namesp::func" then you import that into the current namespace - if you write "using namespace namesp" then you import all variables IN that namespace into the current namespace, and not something called 'namesp'.
<3> s/[l/[k/
<3> ie:
<3> namespace n1 {
<3> namespace n2 {
<3> int x;
<3> } }
<3> namespace n3 {
<3> using namespace n1::n2;
<3> using namespace n1::n4;
<9> it works, i just have to say using namespace comPort
<3> }
<9> not like using comPort as you said
<3> err
<3> I meant:
<3> namespace n1 { int n4; } and
<3> using n1::n4;
<3> then the first
<3> using namespace n1::n2;
<3> imports n1::n2::x and not "n1::n2"
<3> while the second
<3> using n1::n4;
<3> imports "n1::n4"
<3> So, there is a distinct difference.
<13> n1::n4 imports that one variable
<3> It's not to make it unambigious though...
<13> tells it all n4s to be used from n1
<9> okay, i'll take a look on what you said
<13> n1::n2 tell is to import all variables in namespace n2
<3> If you can write one, you can't write the other, so...
<9> 10x
<13> any variables that'd be defined in more than one namespace are defined as their n2 values... right?
<3> Kinda like: typename typedef foo<T>::type type;
<3> argh
<3> damn typos
<3> I meant:
<3> Kinda like: typedef typename foo<T>::type type;
<13> wait. that's right... if you're using a namespace, you can't access variables/functions/etc. defined in another namespace without a direct call, right?
<3> then the 'typename' is not really necessary to understand it either - but it's still written.
<7> what's a "direct call"
<13> direct call: n1::n4 when in namespace n2
<7> n4 is a variable?
<9> another question:
<13> yes, and n1 and n2 are namespaces
<9> what is the diff between:
<9> 1)
<9> namespace bla
<9> {
<7> you can do using n1::n4; in n2
<9> #include "some.h"
<9> ...
Return to
#c++
or
Go to some related
logs:
#windows
#MissKitten
OldMonk linux
download inter explorer 7
#linuxhelp
#mysql
horde unable to connect to localhost:106 passwd/lib/Driver/poppassd.php
#chatzone
#chatzone
tfimx
|
|