Problem with VAR

Comments

• jazzed Posts: 11,803

  2009-05-12 00:28 edited 2009-05-12 00:28

  Maybe you can create a very short reproduce-by code snippet to share ? It would be very useful to see that.
  
  ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  --Steve
  
  
  Propalyzer: Propeller PC Logic Analyzer
  http://forums.parallax.com/showthread.php?p=788230
• RogerInHawaii Posts: 87

  2009-05-12 00:31 edited 2009-05-12 00:31

  Yes, it would be nice to be able to do that. But this is one huge program and I'm only encountering it in one particular place in the program. So I really doubt that I can come up with a small snippet that would reproduce it. It's got me baffled.
• jazzed Posts: 11,803

  2009-05-12 00:35 edited 2009-05-12 00:35

  Maybe it's time to try Hanno's ViewPort debugger?
  
  ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  --Steve
  
  
  Propalyzer: Propeller PC Logic Analyzer
  http://forums.parallax.com/showthread.php?p=788230
• Philldapill Posts: 1,283

  2009-05-12 01:16 edited 2009-05-12 01:16

  Roger, are you sure that these two places where you "call" _A are in the same cog? Those variables are cog specific, and if you are running two different instances of that code, that could be your problem.
• RogerInHawaii Posts: 87

  2009-05-12 02:41 edited 2009-05-12 02:41

  They're in the same cog. But I finally realized the problem. And it was due to a typo! Aaaarrrggghh!
  
  I think I'm going to come out with a line of T-shirts that says "Typos Happen".
• CassLan Posts: 586

  2009-05-12 02:44 edited 2009-05-12 02:44

  That sounds like a great shirt
  
  Rick
• mpark Posts: 1,325

  2009-05-12 05:29 edited 2009-05-12 05:29

  I think the shirt should have a typo.
• Phil Pilgrim (PhiPi) Posts: 23,514

  2009-05-12 06:20 edited 2009-05-12 06:20

  It has two already.
  
  -Phil
• QuattroRS4 Posts: 916

  2009-05-12 08:59 edited 2009-05-12 08:59

  Nice catch Phil!
  
  Regards,
  John
  
  ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  'Necessity is the mother of invention'
  
  Those who can, do.Those who can’t, teach.
• StefanL38 Posts: 2,292

  2009-05-12 11:39 edited 2009-05-12 11:39

  Hello,
  
  I want to correct a detail.
  
  VAR-variables are NOT cog-specific they are object-specific.
  
  This is a big difference ! As long as methods are called from the SAME object(= same *.SPIN-file)
  all VAR-variables defined in that *.SPIN-file are accessible even ACROSS cogs !
  
  here is a small democode that shows that
  
  

  CON
    _clkmode = xtal1 + pll16x
    _xinfreq = 5_000_000
  
    
  VAR
    long heart_stack[noparse][[/noparse] 20]
    long CogStack1[noparse][[/noparse] 20]
    long CogStack2[noparse][[/noparse] 20]
    
    long MyTestVar
  
  OBJ
    debug : "FullDuplexSerial"
  
  
  PUB Main
  'the FIRST PUB-Method inside a spinfile is ALWAYS the startpoint where the program starts to run
    debug.start(31, 30, 0, 9600)
    
    MyTestVar := 100
    debug.str(string("Start MyTestVar="))
    debug.dec(MyTestVar)
    debug.Tx(13)
  
    cognew(M1,@CogStack1)
    cognew(M2,@CogStack2)
    
    repeat
      waitcnt(clkfreq + cnt)
      debug.str(string("MyTestVar="))
      debug.dec(MyTestVar)
      debug.Tx(13)
  
  
  
  PUB M1
    repeat
      waitcnt(ClkFreq * 3 + cnt)
      MyTestVar := 1
  
  
  PUB M2
    repeat
      waitcnt(ClkFreq * 5 + cnt)
      MyTestVar := 2
  
  
  

  
  
  
  best regards
  
  Stefan
• mpark Posts: 1,325

  2009-05-12 15:10 edited 2009-05-12 15:10

  Phil Pilgrim (PhiPi) said...
  It has two already.
  
  -Phil

  
  Huh? I don't get it.
• Phil Pilgrim (PhiPi) Posts: 23,514

  2009-05-12 15:25 edited 2009-05-12 15:25

  "Happen" is capitalized, and there's no period at the end of the sentence. (Yeah, I know. It's horribly pedantic, isn't it? Moreover, the claim could be made that it's a title or headline.)
  
  This same shirt could be adapted for blood bank workers as well: Type Os happen.
  
  -Phil