|
|
|
|
Joined: May 2003
Posts: 2,265
Hoopy frood
|
Hoopy frood
Joined: May 2003
Posts: 2,265 |
i think mirc should stay as it is, but i also think it would be a good idea to make the dialog layout code, a proper language as its so much easier than c++ and the like =o\, then just use different code to make it work :tongue:
new username: tidy_trax
|
|
|
|
|
Joined: Jun 2003
Posts: 10
Pikka bird
|
|
OP
Pikka bird
Joined: Jun 2003
Posts: 10 |
as you wish...
i think that i offten tells you my opinion...
|
|
|
|
|
Joined: Dec 2002
Posts: 2,809
Hoopy frood
|
|
Hoopy frood
Joined: Dec 2002
Posts: 2,809 |
C++ file handling is fast and easy, I find it much easier than mIRC.
ofstream out("thefile.txt");
out << "this is some text" << endl;
out << "Now a number" << 10 << endl;
out.close();
Is that really so bad?
And as for sockets, you can either get a stream-based socket class (there are a bunch available), or you can *gasp* use .NET
|
|
|
|
|
Joined: May 2003
Posts: 2,265
Hoopy frood
|
|
Hoopy frood
Joined: May 2003
Posts: 2,265 |
thats not so bad because you know it though, to me that doesnt make any sense at all, even thought i am learning c++ now as well.
new username: tidy_trax
|
|
|
|
|
Joined: Jan 2003
Posts: 3,012
Hoopy frood
|
|
Hoopy frood
Joined: Jan 2003
Posts: 3,012 |
im trying to get into winAPI, but the demo of the .NET compiler I got with a book is on a dvd cd, and my computer doesn't read it. Must be a new kinds of copyrighting on Microsoft's part, but until I can get the compiler--my book is useless. >:\ Would you have any suggestions codematr?
-KingTomato
|
|
|
|
|
Joined: Dec 2002
Posts: 2,809
Hoopy frood
|
|
Hoopy frood
Joined: Dec 2002
Posts: 2,809 |
Buy MSVC++ .NET 
|
|
|
|
|
Joined: Jan 2003
Posts: 3,012
Hoopy frood
|
|
Hoopy frood
Joined: Jan 2003
Posts: 3,012 |
Do you have a ballpark figure?
-KingTomato
|
|
|
|
|
Joined: Jun 2003
Posts: 114
Vogon poet
|
|
Vogon poet
Joined: Jun 2003
Posts: 114 |
File handling IS easy, if you want to read or write info. It gets a little more complicated when you want to do both. mIRC's file handling is just a little bit easier when you want to store and retrieve specific info from a file. But, I was bored so I wrote my own function to store and retrieve from a file pretty much the same way.
As for sockets... they are a manifestation of satan himself in C++. I have no idea what .NET is like, because I have no need to program sockets for Windows. I use a Linux compiler. Umm.. .NET may be available on Linux, I have no clue. I haven't really found much out about .NET.
Actually, my problem with sockets is finding a good reference on them. If there was a website or help file that had a good, solid explanation of sockets and how to implement them my life would be easier.
-------------
I am the self-appointed God of needlessly complex mIRCscript.
|
|
|
|
|
Joined: Dec 2002
Posts: 2,809
Hoopy frood
|
|
Hoopy frood
Joined: Dec 2002
Posts: 2,809 |
For Windows I have Network Programming for Microsoft Windows Second Edition, it's an excellent book that covers socket programming under all versions of Windows using standard WinSock API as well as .NET and how to use it in C, C++ and C#. For *nix, Unix Network Programming Second Edition Volume 1 - Networking APIs Sockets and XTI, Linux Socket Programming, Linux Socket Programming by Example, and TCP/IP Sockets in C Practical Guide for Programmers. Scrap up the money to buy those and you should never have a socket problem you can't handle
|
|
|
|
|
|
|
