Skip to content
Snippets Groups Projects
  1. Nov 16, 2021
    • Josh Soref's avatar
      pbx: Spelling fixes · 3685e556
      Josh Soref authored
      Correct typos of the following word families:
      
      process
      populate
      with
      africa
      accessing
      contexts
      exercise
      university
      organizations
      withhold
      maintaining
      independent
      rotation
      ignore
      eventname
      
      ASTERISK-29714
      
      Change-Id: I90eacc5bc3dcf75a9c898cfb85164f37dec08345
      3685e556
  2. Dec 22, 2017
  3. Dec 22, 2010
  4. Oct 04, 2010
  5. Dec 17, 2008
  6. Sep 04, 2008
    • Steve Murphy's avatar
      Merged revisions 141094 via svnmerge from · ec25f4be
      Steve Murphy authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
      r141094 | murf | 2008-09-04 17:15:07 -0600 (Thu, 04 Sep 2008) | 70 lines
      
      (closes issue #13357)
      Reported by: pj
      Tested by: murf
      
      (closes issue #13416)
      Reported by: yarns
      Tested by: murf
      
      If you find this message overly verbose, relax, it's probably
      not meant for you. This message is meant for probably only
      two people in the whole world: me, or the poor schnook that
      has to maintain this code because I'm either dead or unavailable
      at the moment.
      
      This fix solves two reports, both having to do with embedding
      a function call in a ${} construct. It was tricky because the
      funccall syntax has parenthesis () in it. And up till now,
      the 'word' token in the flex stuff didn't allow that, because
      it would tend to steal the LP and RP tokens. To be truthful,
      the "word" token was the trickiest, most unstable thing in
      the whole lexer. I was lucky it made this long without complaints.
      I had to choose every character in the pattern with extreme
      care, and I knew that someday I'd have to revisit it. Well,
      the day has come.
      
      So, my brilliant idea (and I'm being modest), was to use the 
      surrounding ${} construct to make a state machine and capture 
      everything in it, no matter what it contains. But, I have to now
      treat the word token like I did with comments, in that I turn
      the whole thing into a state-machine sort of spec, with new
      contexts "curlystate", "wordstate", and "brackstate".
      
      Wait a minute, "brackstate"? Yes, well, it didn't take very many
      regression tests to point out if I do this for ${} constructs,
      I also have to do it with the $[] constructs, too.
      
      I had to create a separate pcbstack2 and pcbstack3 because
      these constructs can occur inside macro argument lists, and
      when we have two state machines operating on the same structures
      we'd get problems otherwise. I guess I could have stopped at
      pcbstack2 and had the brackstate stuff share it, but it doesn't
      hurt to be safe. So, the pcbpush and pcbpop routines also now
      have versions for "2" and "3".
      
      I had to add the {KEYWORD} construct to the initial pattern for
      "word", because previously word would match stuff like "default7",
      because it was a longer match than the keyword "default". But,
      not any more, because the word pattern only matches only one or
      two characters now, and it will always lose. So, I made it the
      winner again by making an optional match on any of the keywords
      before it's normal pattern.
      
      I added another regression test to make sure we don't
      lose this in future edits, and had to fix just one regression,
      where it no longer reports a 'cascaded' error, which I guess
      is a plus.
      
      I've given some thought as to whether to apply these fixes to
      1.4 and the 1.6.x releases, vs trunk; I decided to put it in
      1.4 because one of the bug reports was against 1.4; and it
      is unexpected that AEL cannot handle this situation. It actually
      reduced the amount of useless "cascade" error messages that
      appeared in the regressions (by one line, ehhem). There is
      a possible side-effect in that it does now do more careful
      checking of what's in those ${} constructs, as far as matching
      parens, and brackets are concerned. Some users may find a an
      insidious problem and correct it this way. This should be 
      exceedingly rare, I hope.
      
      
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@141115 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      ec25f4be
  7. Aug 08, 2008
    • Steve Murphy's avatar
      Merged revisions 136726 via svnmerge from · a40f1cc1
      Steve Murphy authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
      r136726 | murf | 2008-08-07 18:15:34 -0600 (Thu, 07 Aug 2008) | 32 lines
      
      
      (closes issue #13236)
      Reported by: korihor
      
      Wow, this one was a challenge!
      
      I regrouped and ran a new strategy for
      setting the ~~MACRO~~ value; I set it once
      per extension, up near the top. It is only
      set if there is a switch in the extension.
      
      So, I had to put in a chunk of code to detect
      a switch in the pval tree.
      
      I moved the code to insert the set of ~~exten~~
      up to the beginning of the gen_prios routine, 
      instead of down in the switch code.
      
      I learned that I have to push the detection
      of the switches down into the code, so everywhere
      I create a new exten in gen_prios, I make sure
      to pass onto it the values of the mother_exten
      first, and the exten next.
      
      I had to add a couple fields to the exten
      struct to accomplish this, in the ael_structs.h
      file. The checked field makes it so we don't
      repeat the switch search if it's been done.
      
      I also updated the regressions.
      
      
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@136746 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      a40f1cc1
  8. Jun 03, 2008
  9. Apr 21, 2008
    • Steve Murphy's avatar
      (closes issue #12467) · c0b8f57b
      Steve Murphy authored
      Reported by: atis
      Tested by: murf
      
      This upgrade adds the ~~ (concatenation) string operator to expr2.
      While not needed in normal runtime pbx operation, it is needed when
      raw exprs are being syntax checked. This plays into future syntax-
      unification plans. By permission of atis, this addition in trunk 
      and the reason of why things are as they are will suffice to close
      this bug.
      
      I also added a short note about the previous addition of "sip show sched"
      to the CLI in CHANGES, which I discovered I forgot in a previous commit.
      
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@114423 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c0b8f57b
  10. Mar 18, 2008
    • Steve Murphy's avatar
      Merged revisions 109309 via svnmerge from · 4e29ae88
      Steve Murphy authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
      r109309 | murf | 2008-03-18 00:37:15 -0600 (Tue, 18 Mar 2008) | 17 lines
      
      (closes issue #11903)
      Reported by: atis
      
      Many thanks to atis for spotting this problem and reporting it.
      The fix was to straighten out how items are placed on and removed
      from the file stack. Regressions as well as the provided test case
      helped to straighten out all code paths. valgrind was used to make
      sure all memory allocated was freed.
      
      Sorry for not solving this earlier. I got distracted.
      
      Added the ntest23 regression test, which is mainly a copy of ntest22, 
      but with a few juicy errors thrown in, to replicate the kind of 
      error that atis spotted.
      
      
      
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@109357 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      4e29ae88
  11. Nov 27, 2007
  12. Nov 26, 2007
  13. Oct 26, 2007
    • Steve Murphy's avatar
      Merged revisions 87168 via svnmerge from · c9f3efc3
      Steve Murphy authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
      r87168 | murf | 2007-10-26 10:34:02 -0600 (Fri, 26 Oct 2007) | 1 line
      
      closes issue #11086 where a user complains that references to following contexts report a problem; The problem was REALLy that he was referring to empty contexts, which were being ignored. Reporter stated that empty contexts should be OK. I checked it out against extensions.conf, and sure enough, empty contexts ARE ok. So, I removed the restriction from AEL. This, though, highlighted a problem with multiple contexts of the same name. This should be OK, also. So, I added the extend keyword to AEL, and it can preceed the 'context' keyword (mixed with 'abstract', if nec.). This will turn off the warnings in AEL if the same context name is used 2 or more times. Also, I now call ast_context_find_or_create for contexts now, instead of just ast_context_create; I did this because pbx_config does this. The 'extend' keyword thus becomes a statement of intent. AEL can now duplicate the behavior of pbx_config,
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@87187 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c9f3efc3
  14. Oct 24, 2007
  15. Oct 03, 2007
    • Steve Murphy's avatar
      Merged revisions 84511 via svnmerge from · 3ffa04bb
      Steve Murphy authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
      r84511 | murf | 2007-10-03 08:23:00 -0600 (Wed, 03 Oct 2007) | 1 line
      
      closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@84512 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      3ffa04bb
  16. Sep 29, 2007
  17. Aug 23, 2007
    • Steve Murphy's avatar
      an unreported crash I debugged, looked like it was backing up way too far... · 83e28341
      Steve Murphy authored
      an unreported crash I debugged, looked like it was backing up way too far after hitting the syntax error. An inspection of the code revealed that error tokens in lists were not rearranged when the rules were rearranged as part of a code neatening-up process. By moving the error tokens to where they should be, I also reduced the number of shift/reduce conflicts to 3 instead of 8. This introduces subtle differences in error messages, so the regressions had to be updated.
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@80649 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      83e28341
  18. Aug 15, 2007
  19. Aug 14, 2007
  20. Jun 20, 2007
  21. Jun 05, 2007
  22. Jun 04, 2007
  23. May 03, 2007
  24. Mar 26, 2007
  25. Mar 03, 2007
  26. Feb 18, 2007
  27. Jan 02, 2007
  28. Dec 28, 2006
  29. Dec 27, 2006
  30. Nov 13, 2006
  31. Oct 13, 2006
  32. Oct 04, 2006
  33. Oct 03, 2006
  34. Sep 27, 2006
  35. Aug 31, 2006
  36. Aug 25, 2006
  37. Aug 12, 2006
Loading