-
Posts
7,103 -
Joined
-
Days Won
88
Content Type
Forums
Downloads
Forum Articles
Events
Everything posted by TheDcoder
-
I wanted to do this in public so that freenode staff can see the proof. I strongly disagree, The IRC is community much larger and active, There many people there who like free software (this is also the meaning of "free" in freenode). I also disagree that they should redirect to the forums, atleast the IRC community should not, Forums and IRC serve different purposes as I already explained earlier. You can understand better if you try using IRC, The AutoIt IRC Community is slowly growing too, Many of its participants agree that having a IRC Community is good for AutoIt Enthusiasts. Anyways, This is why I bumped this thread, to create discussion.
-
@Jos Oh, I forgot to check for updates lol. Will update now...
-
@iamtheky I don't want to change the title and confuse the actual purpose of this thread. I bumped it for 2 reasons: 1. To keep this thread alive (so that @Jon can see it when he returns). 2. To create awareness of freenode and IRC. I could bump one of my other threads but by bumping threads serves as a dual purpose bump.
-
@Jos Well... I just checked and it works fine now, I honestly don't know why ... Maybe I forgot to reopen the file after move the file?
-
Hello, Today I discovered a bug in SciTE: https://www.youtube.com/watch?v=AbDMXTx5R-k It was working fine until I started using it in Git... Thanks in Advance, TD
-
Version 0.1 rev 4
256 downloads
Features: Lightweight & Simple. Native support for logging. Full compliance with RFC 2812 and IRCv3.1. Fully tested. Ability to parse server messages. Open source and Unlicenced. Coded with Best Coding Practices in mind. Support for major IRC networks. SASL Authentication Supported! ..etc. Planned Features: Support for DCC and Direct P2P file transfer Colors More functions for Atheme services (NickServ, ChanServ etc.) ...etc. -
Hello! I have been busy with establishing the IRC Community for AutoIt... I thought that ##AutoIt needs a bot with lot of neat features, I made a simple one using @rcmaehl's UDF but it lacked many features which I wanted so I made a new UDF for myself lol. Features: Lightweight & Simple. Native support for logging. Full compliance with RFC 2812 and IRCv3.1. Fully tested. Ability to parse server messages. Open source and Unlicenced. Coded with Best Coding Practices in mind. Support for major IRC networks. SASL Authentication Supported! ..etc. Planned Features: Support for DCC and Direct P2P file transfer Colors More functions for Atheme services (NickServ, ChanServ etc.) ...etc. Download GitHub https://github.com/TheDcoder/IRC-UDF-for-AutoIt Enjoy! TD P.S I am newbie at GitHub so the repo might look weird
-
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
Yeah, that is true . but it would make it nicer, making those "not nice" things nice, it would contribute to making AutoIt a "nice" language P.S Sorry for late reply, I was busy with my project. -
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
@gil900 I don't think it would be nice if it does not get deleted -
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
Yup, That is what I told in in above post . From what @gil900 pointed out, there is a risk that it (The Array Literal) might be overwritten in memory before it gets processed resulting in malfunction. So it makes implementing Array Literals more hard... but not that hard, here is a simple solution: When the Interpreter parses a Array Literal, it will create a new temporary variable (pointer for the Array Literal) and deletes the variable (or pointer) after the completion of the operation (like evaluation of the expression or returning of the function). This way we could avoid the accidental overwriting of the variable . P.S I am aware that implementing it programmatically would be difficult but IMHO its worth it. -
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
@gil900 Oh ! So the pointer gets deleted and the array in the memory is open for overwriting. Am I correct? -
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
@czardas Ugh... I messed up with the example, I was sleepy and tried working on my project at that time... Fixed it now lol. -
@Kronitron Write code which does not involve mouse clicks & keyboard automation
- 14 replies
-
- detect
- orientation
-
(and 3 more)
Tagged with:
-
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
@JohnOne True, it is possible to do in python... @czardas That example was meant to demonstrate that ByRef works with non-variable objects. -
Is it a Good Idea?: A new way to indicate arrays
TheDcoder replied to TheDcoder's topic in AutoIt Technical Discussion
why? I am totally clueless Yes, I am aware of that and I tested for it in the past by passing an array made by a function: #include <Array.au3> Global $aArray[2] = [1, 2] _ArrayDelete(_ArrayAdd($aArray, 3), 2) (AU3Check does show an error "_ArrayDelete() called with Const or expression on ByRef-param(s)" but if you bypass AU3Check the script runs without any problems.) How? -
Hello! After a long time, I bring you yet another IIAGI topic . Today its about indicating(?) arrays... here is a visual example: "This is an example for a string" 1337 ; An integer 13.37 ; Integer ["This", "is", "an", "example", "for", "an", "array"] ; All work except the Array's example :( All the examples (each separated by a line) can be passed to a function or a variable without the help of a variable except the array example... That shouldn't be like that! We can use the way (which I just demonstrated above) in many ways, here is one way I can think of now: Local $aInitialArray = [1, 2, 3] _ArrayConcatenate($aInitialArray, [4, 5, 6]) I would love to see this implemented ... I honestly don't see reason for this NOT to be implemented .