Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

Issue Confirmations

  • Yes (1)No (0)
Photo

loop warning

Posted by Hercules Bot on 15 June 2012 - 02:20 PM

Originally posted by wend
revision 16303

for (.@i = 0; .@i < 20; .@i++) {

warning:
[Warning]: Unexpected type for argument 2. Expected label.
[Debug]: Data: number value=1
[Warning]: Found more arguments than necessary.
[Debug]: Function: jump_zero
[Debug]: Source (NPC): Test#1 at prontera (109,94)
[Error]: script: jump_zero: not label !
[Debug]: Source (NPC): Test#1 at prontera (109,94)

Originally posted by malufett
AFAIK ".@i++" is not supported..only 'set .@i, .@i+1' or '.@i = .@i+1'

Originally posted by wend
for (.@i = 0; .@i < 10; .@i = .@i + 1) {
same warning

Originally posted by Euphy
According to Epoque's post, though, .@i++ should be working.

Originally posted by malufett
Thanks for the info Euphy...

ok now I found out the cause its not the incremental operator...

.@i = 0; then use in a condition like .@i<1

this set the warning...lets wait for Epoque to fix it or maybe I'll try to understand its implementation and do the fix...

Originally posted by wend
Everyone forgot about it? Many scripts does not work..

Originally posted by Xantara
Might be related to [bug:5740] ( just posting for further info... if it helps ><;; )

Originally posted by GreenBox
The VM was not pushing back a reference to the modified variable on unary operators and assignment operations, now pushing the reference the stack is getting corrupted :S

Originally posted by Cookie
Just a FYI,

I received the same error. Here's an example -
@mapname$ = strcharinfo(3);
if (@mapname$ == "izlude")
{
dothis;
}
Boom! jump_zero nonsense.

Point of the code above is that, it really didn't like mixing set's with the new engine. Even though, as Epoque's post says, they should be all in the same family as @i = 0; is the same as set @i, 0; if I'm not mistaken.

Edited by Cookie, 27 June 2012 - 03:13 PM.


Originally posted by Jelly
Started at : 15 June 2012
Can you damn fix this?  
We can't recompile server without fix /ok  

Why sometimes rA ppl fix something and crush another things?

Edited by Jelly, 19 July 2012 - 02:08 PM.


Originally posted by Euphy
Jelly, are you serious?  This is an open-source emulator, nobody is getting paid for their work.  Relax, somebody will get to this when they have time.

Originally posted by Jelly
Ton of scripts can not work without this fix.
And ofc we can't recompile server (for new revision) cauze all stuff can't work.

Originally posted by Euphy
There are a grand total of 0 scripts in our SVN that use this...

Originally posted by Ind
jelly should you troll any bug reports further and i'll have your arse banned, this is your first and final warning. i do not tolerate this.

Originally posted by Mysterious
Jelly, the staff have tons and TONS of other Bug Fixes, Projects, and other necessary things that need to be really done. As mentioned throughout rAthena this is a Free-OPEN SOURCE project and not paid. Every single Administrator and Developer here are doing work for FREE. =/

Now, as Euphy said, I personally have no scripts in my SVN that use any such code that relates to this. So I don't experience anything like this. Following this, your SVN was severely outdated at the time. Try updating it and take out useless NPCs that aren't coded properly =/.


I should mind my own 2-sense. Sorry.

Edited by Mysterious, 21 July 2012 - 01:19 AM.


Originally posted by Ind
should be fixed in [rev=16555]