Forums Developers Script Documentation

Anyone know where I can get printable docs on Mirc's scripting features?

thanks.

Open mIRC and type /help

I'm looking for something a little more comprehensive.

How much more comprehensive can you get? I mean the helpfile does describe... everything!

nope, regex/regsub,GET/POST/HEAD.

GET/POST/HEAD? Are you talking HTTP protocol? If so, *insert laugh here* why are you? Guess what else the helpfile doesn't document, the FTP protocol, the NNTP protocol, the NTP protocol, and thousands of other protocols. Why should mIRC document HTTP? It has NOTHING to do with mIRC. If the helpfile documented every protocol in existence it would easily total well over 100GB in size.

possibly because this is the most commonly used things in sockets?

Ok so mIRC should include the 5MB of documentation available on HTTP? Thats just stupid.

5mb? heh,GET = directory(url) of the info you want to get,POST = directory(url) of the place where you want to post info,HEAD = dunno.
with the explanation of head added i dont think thats too much to add?

LOL yes the entire HTTP protocol is summed up in 3 lines like that.

According to RFC2616 the following methods exist in HTTP1.1:
OPTIONS
GET
HEAD
POST
PUT
DELETE
TRACE
CONNECT

And an example of the real definition, rather than your simplistic nonsense, GET is described as:
The GET method means retrieve whatever information (in the form of an
entity) is identified by the Request-URI. If the Request-URI refers
to a data-producing process, it is the produced data which shall be
returned as the entity in the response and not the source text of the
process, unless that text happens to be the output of the process.

The semantics of the GET method change to a "conditional GET" if the
request message includes an If-Modified-Since, If-Unmodified-Since,
If-Match, If-None-Match, or If-Range header field. A conditional GET
method requests that the entity be transferred only under the
circumstances described by the conditional header field(s). The
conditional GET method is intended to reduce unnecessary network
usage by allowing cached entities to be refreshed without requiring
multiple requests or transferring data already held by the client.

The semantics of the GET method change to a "partial GET" if the
request message includes a Range header field. A partial GET requests
that only part of the entity be transferred, as described in section
14.35. The partial GET method is intended to reduce unnecessary
network usage by allowing partially-retrieved entities to be
completed without transferring data already held by the client.

The response to a GET request is cacheable if and only if it meets
the requirements for HTTP caching described in section 13.

See section 15.1.3 for security considerations when used for forms.

Stop speaking when you haven't a clue what you are talking about.

i dont have a clue what im talking about?
i must imagine that my mirc webpage editor works then

for a guy that doesnt know what the HEAD is in http your claiming uve designed a webpage editor in mirc? gimme a break. 3 weeks ago u were beggin for help with sockets claiming uve never used em before.

what can i say? im a fast learner
i tried using head n it just brought up a loada stuff that i dont care about.

For $regex try www.pcre.org

What is your point? A monkey CAN drive a car, it doesn't mean he knows HOW to drive a car. For all I know, you stole all your code from someone else. Not to mention the fact that almost every single day you were basically here having us write code for you...

whenever someone gives me cod ei dont use it, i stick it in a text file with the rest to learn from,if you think im a ripper i couldnt care less, as long as i know i'm not why should it bother me?
for all i know your not the real author of unreal.

I didn't say you were a ripper, I guess you forgot the question you posed. You said if you don't know HTTP (which you clearly don't) how did you manage to make an http script. I provided an answer, you could have stolen the code from others.

As for saying I'm not the author of UnrealIRCd, all you have to do is email my codemastr at unrealircd dot com email address and I'll gladly respond to you letting you know that it is in fact me.

thats what a ripper is....
why would i need to know everything in the http protocol when i only use get post and delete :tongue: ?

You could print out the areas of the help file and mIRC's FAQ, as well as investigate the numerous tutorials around and about. Here are a couple, and use the search feature here, set to All Forums, All Dates, using tutorial as search term, as there have been others mentioned.

http://helpdesk.zaz.net/documents/tutorials.php
http://www.mishscript.de
http://www.ircworks.com/jeepster.htm (jeepz numerics

yegawds, enough! take the bickering private, none of this is remotely answering the question asked.

The help file and FAQ cant contain every single thing a user might conceivably ever use. Accept it. Move on.

i know, he said that the help file documentated everything in mirc, i just said it didnt.

ok, i'll explain. COMPREHENSIVE does NOT mean everything and every detail. (example: regex and regsub ARE in the help file, and as i pointed out to you before:" It is beyond the scope of this help file to explain how Regular Expressions work"). Codemastr's obvious intent was what better starting place to find the MOST amount of info in one place.

No help file or FAQ is going to hold your hand and detail every possible thing you might ever want to someday use, in every potential way and with what. That does not mean they are not comprehensive.

.......
it wasnt me who suggested it describe everything, or say that it did.

Regex is PCRE, not mIRC. Thats why the helpfile doesn't document it.

from the help file: Regular expressions are basically a grammar that can be used to perfom complicated pattern matching operations. You should already know how to use Regular expressions before using the identifiers below.

why even put it in the help file then?,he could just put it in the command list on this site.

Are you just looking to drag this argument out or do you honestly not understand why the PCRE documentation isn't included in mIRC?

PCRE's documentation isn't included in mIRC's help file for the same reason that the HTTP protocol documentation isn't included in mIRC's help file for the very same reason that the detailed instructions needed to write a mIRC-compatible DLL to control a robotic arm that I stole from NASA to open up my fridge and deliver me a cold beer upon request aren't included in mIRC's help file.

All three are equally beyond the scope of what mIRC's documentation.

Khaled documents features he's added to let scripters know how he's chosen to implement a certian feature. The burdon falls on the scripters to understand why you'd want to use the feature and what is possible when using the feature. The same is true of every language in existance.

-c

In addition to d00d, features are added in the help file to notify a user of their existance, not teach you how to use them. There are some things you should have previous knowledge about.

If I look in the help file for the "compatability"of sockets, i can find it. Its not there to teach you how to use it, its there to show you how to use it.

Just like something as simple as strtok. I open my compiler and type strtok(, it will give me a popup with the neccisary information. Now, should it give me all the documentation and exaples on how to use it also? No. All it tells me is how parameters should be passed, and what i need to do to get it to work--the rest is knowledge gained.

Examples in the help files are there (IMO) due to the generosity of Khaled. He understands many, many users take it apon themselves to learn the mirc language, and understand peole who have never programmed in thier life will be attemping these functions. The fact that he needs to explain how every supported function, alias, and identifier is used is assinine.

I've said my peace, im done. Sorry for the long post but, eyy.. Ive got some free time to kill.

Thanks. Some of that stuff wil help.

you're welcome

thats not what i said,i said that there's no point putting it in the help file when it doesn't help :tongue:

$regex help from the help file is the same as DLL support. mIRC supports both and the help file performs its role by providing basic help to get people off the starting blocks. There is nothing comprehensive there because, as has been stated, it's outside the thrust of what the help file is for.

LMAO, doesn't help? The only person(s) it doesn't help are those who dont know how to use it in the first place. if you dont know how to use it in the first place, why are you even looking at it? Thats like me trying to learn win api by looking at a function call that (im not sure hows it done yet, but just for example's sake) calls a dialog window. Its not going to happen.

im saying that $regex shouldnt be in the help file if it doesnt help.

So you want the regex identifiers to be undocumented because they don't explain regular expressions?! Should $dll also be undocumented because it doesn't teach you C, C++, C#, VB, Object Pascal, ASM or any other langauge with which a DLL could be made and used with that command?

The regular expressions section of the helpfile does help. It helps people who already know regular expressions to learn how they can use regexes within mIRC.

forget i said anything.
got better things to do than argue with ya;\

you mean "better things to do than [lose an] argument with ya"
EDIT:
Such as increase post count, make pointless ramblings, post code that 90% of the time is wrong and unrelated to the topic... etc etc