Mod Archive Forums

Music Production => MilkyTracker => Tracking => MilkyTracker Bug Reports => Topic started by: sverx on September 02, 2010, 12:02:07

Title: Bad Dxx behavior when xx is hex...
Post by: sverx on September 02, 2010, 12:02:07

Hello
  I just found out this problem in a 0.90.85 running on an XP. If I specify a D2A I would expect to jump to line number 2A hex (42 dec.) but it jumps to line 1E hex (30 dec) just like if it is taking the first digit (2) as decimal and the second (A) as hex thus making 20+10=30. I guess it should consider the whole value (2A) hex instead, or am I wrong?
Keep up the good work :)

Title: Re: Bad Dxx behavior when xx is hex...
Post by: sverx on September 02, 2010, 12:14:59

Wow, sorry, I just found out that FT2 does the same... that's incredible.
Well, at least this is not a MT bug :D

Bye!

Title: Re: Bad Dxx behavior when xx is hex...
Post by: pailes on September 02, 2010, 12:58:05

It's been like that since the good old amiga .mod days. It's all about heritage ;)

Title: Re: Bad Dxx behavior when xx is hex...
Post by: sverx on September 02, 2010, 14:11:30

I'm a newbie, you know ;D
So actually Dab means a*10+b even if a or b (or both) are hex.
Not a big impact... I had to comment one line in libxm7 code to fix that :)