Adding Exclusive OR to ASH

What should we do about XOR in ASH?

  • Don't bother adding XOR

    Votes: 3 25.0%

  • XOR is ^ and expt is ** or a function.

    Votes: 7 58.3%

  • XOR is ^^ and expt remains ^

    Votes: 1 8.3%

  • None of the above

    Votes: 1 8.3%
  • Total voters
    12
  • Poll closed .
Does anyone know of a good way, on Windows, to search through a bunch of files looking for a certain string? I would like to avoid having to open up every script I have and doing a search and replace for ^...
 
findstr /i /c:"<text to search for>" *

For example: findstr /i /c:" ^ " *
Searches for the ^ symbol with a space around it in every file in whatever folder you're in. After you clean up those, you can do it without the spaces, which will find many more matches.

Technically, the /i isn't needed for searching symbols, since that means that your text is marked case insensitive. Skip if you like... I toss it in as a standard thing since it's easier not to think about it too much.
 
Thanks. That was a rather useful command. autobasement, farm and the OCD-helper script seems to have been the only ones affected.
 
I'm back from my trip and so, in theory, it's time to add this; the "transition" period for script authors, in which both ** and ^ act as pow() has passed. Have all the "major" scripts been updated to use **, so that users of them will not suffer when ^ no longer is pow()? Or are we simply expecting cries of anguish when I remove ^ as pow() and unmodified scripts no longer work with current builds?

Considering that I see no new version of zlib, for example, I think we are operating under the second scenario... :)
 
Well, I think zarqon was waiting for his relay update thing to be sorted to release new bits... I think we'll end up with a wide variety of screams initially, and then they'll die down as people either fix their own scripts (cause that'll happen! really!) or as updates are released. But no, most of them haven't had official updates, far as I've seen.
 
Was there an outstanding question regarding the various evaluator functions? I think I recall seeing that someone was waiting on word for whether those would be changed to use ** in place of ^, but I could be crazy (I've been awake long enough).

Edit: yup, on the previous page by zarqon. I assume that's what zlib is waiting on.
 
Last edited:
I'll just leave the evaluators with ^; they are never going to have arithmetic logic operations, I expect.
 
Ok -- that is what I was waiting on. I just thought it would be confusing for one ASH function to use ^ even though ASH uses **. It's less to change on my end, though, so no complaints.

I'll post the updated ZLib right now!

EDIT: And done.
 
Last edited:
Let it begin, indeed. I think this is the first change to Mafia that was not backwards compatible.
 
You must log in or register to reply here.
Back
Top