🚀 go-pugleaf

Hi everybody,
I decompiled a class file (using 3 different decompilers for accurancy), and
every time I got the same source code, there is something amazing in it, it
has "goto" instruction! how can it be?
does JVM (as executor) supports "goto" instruction, but no standard compiler
supports it yet? so a custom compiler can use it?

(I have changed the generated source code refereneced classes for privacy
;))

generated source code (comments are byte-code instuctions, as you can see
there is no byte-code instuctions for "goto"s!)

Amir Pashazadeh.
----------------------------------------------------------------------------

iterator = e.iterator();
// 10 18:aload_0

// 11 19:getfield #19 <Field java.util.List com.e>

// 12 22:invokeinterface #20 <Method java.util.Iterator
java.util.List.iterator()>

// 13 27:astore 4

if(!g.c) goto _L2; else goto _L1

// 14 29:getstatic #195 <Field boolean com.g.c>

// 15 32:ifeq 61

_L1:

com.e e1 = (com.e)iterator.next();

// 16 35:aload 4

// 17 37:invokeinterface #21 <Method java.lang.Object
java.util.Iterator.next()>

// 18 42:checkcast #22 <Class com.e>

// 19 45:astore 5

if(e1.a(s1, this, i))

//* 20 47:aload 5

//* 21 49:aload_2

//* 22 50:aload_0

//* 23 51:iload_3

//* 24 52:invokevirtual #23 <Method boolean com.e.a(java.lang.String, com.a,
int)>

//* 25 55:ifeq 61

return e1;

// 26 58:aload 5

// 27 60:areturn

_L2:

if(!iterator.hasNext())

//* 28 61:aload 4

//* 29 63:invokeinterface #24 <Method boolean java.util.Iterator.hasNext()>

//* 30 68:ifne 35

throw new g(a.b(com.g.b.bf));

// 31 71:new #25 <Class com.g>

// 32 74:dup

// 33 75:getstatic #26 <Field com.a.a>

// 34 78:getstatic #27 <Field java.lang.String com.g.b.bf>

// 35 81:invokevirtual #28 <Method java.lang.String
com.e.b(java.lang.String)>

// 36 84:invokespecial #29 <Method void g(java.lang.String)>

// 37 87:athrow

if(true) goto _L1; else goto _L3

_L3: