If you aren't adding new files or changing the TOC file you don't need to log out or quit WoW to pick up your changes.
Simple fix the error, save the file, and type /reload in game.
thank you for the hint.
but then my next question would be. how do i test arena or bg addons. i know i can enter dungeons by myself but i don't feel like doing hundreds of arena's (and getting my rating dropped) just to fix some bugs.
I recently ran into an issue, not the same as yours, but where testing was a challenge. I ended up mocking/emulating the wow game a bit. If you addon is well structured, it's sometimes possible to do this using some timers, custom datasets, etc. It all depends on your addon.
In my case, I needed to test how my code detects a Shaman dying that also has a soulstone on them (I was implementing support to detect Reincarnation). I ended up basically cheating and making my addon think that I had a Shaman in the group that had a SS on them. Because the entry point was the COMBAT_LOG_EVENT_UNFILTERED event, I just manually made fake entries there in the order I wanted to be able to test out my program's logic.
I think it just checks the combat log for rez spells, so there's no need to have an add-on for each player.
It does not use the combat log, it uses the UNIT_SPELLCAST_* events to deal exclusively with the player, and broadcasts the player's name and target across the comm. The CanRes callback is also player exclusive, and broadcast, so you need LRC to see other people's self res type (Reincarnate, soul stone, Twisting Nether card). You cannot get accurate information any other way, except possibly checking UNIT_AURA, but that wouldn't help you for Reincarnation or Twisting Nether.
Up to this point, the combat log's res information does not return destGUID, so you cannot use the it to detect the target's name. Maybe that will change in 4.2.
If 4.2 makes LibResComm-1.0 obsolete, so be it. But I doubt the full functionality of the lib will be eliminated.