Jump to content

Recommended Posts

It has to do with pointers. If you know C++, you'd understand the difference between an empty string and a null string.

I do happen to know the difference between a null-terminated string and a null pointer, but I don't see where that has anything to do with Autoit. It's not a low-level language. Users aren't supposed to be required to deal with that level of complexity.

If we're not supposed to use the term "null text" or "null string" then the helpfile needs more work than I'm proposing (those terms are currently in the help file). As far as Autoit is concerned, I'll continue to consider that 'null' does exist, and, that "" is both a null string and an empty string at the same time (neither of which 'contain' quotes).

I don't understand why a suggestion to correctly document the action of two Autoit operators results in my repeated education about variable types, addressing modes, pointers and the like. I learned the difference between int, long, float and a string variable when I was 15 in 1975. And none of the lectures I've recieved are to the point.

Are these not facts???

1: The documentation states the only difference between = and == is case-sensitivity.

2: In actuality, the operators behave differently when comparisons involve null (or empty) strings, the null character, or (ASCII) zero.

I'll dispense with my argument, I'm beginning to feel like I'm kicking everyone's puppy. Let the documentation remain stating that the only difference between the = operator and the == operator is case-sensitivity. Maybe I'll pipe in again on one of the future threads where this same question is asked.


Edited by Spiff59
Link to post
Share on other sites

I agree that there are always something in the docs that need clarification. The big problem is that we have enough problems getting people to read them now and the more complexity that's added the more they will tend to shy away from reading it. BTW; the difference between "=" and "==" has been discussed previously. A search of the forums would turn that up.

My big concern with the docs is in making sure that all of the information is in there someplace. If you want that changed then do as was previously suggested and open a Trac ticket with the category set to Documentation. It will be considered, I assure you, but it may or may not be accepted. I've had a few of mine accepted and a few refused.


Question about decompiling code? Read the decompiling FAQ and don't bother posting the question in the forums.

Be sure to read and follow the forum rules. -AKA the AutoIt Reading and Comprehension Skills test.***

The PCRE (Regular Expression) ToolKit for AutoIT - (Updated Oct 20, 2011 ver: - Please update your current version before filing any bug reports. The installer now includes both 32 and 64 bit versions. No change in version number.

Visit my Blog .. currently not active but it will soon be resplendent with news and views. Also please remove any links you may have to my website. it is soon to be closed and replaced with something else.

"Old age and treachery will always overcome youth and skill!"

Link to post
Share on other sites

uh oh, what have I done lol ;p

 "I believe that when we leave a place, part of it goes with us and part of us remains... Go anywhere, when it is quiet, and just listen.. After a while, you will hear the echoes of all our conversations, every thought and word we've exchanged.... Long after we are gone our voices will linger in these walls for as long as this place remains."

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...