NativeEthernet compilation issue with Ethernet.begin(mac ,ip )

[CrazyDog]

I'm sending UDP messages successfully using the NativeEthernet library on a T4.1 to my windows 10 PC LAN as verified by Wireshark. The problem is that the Identical Ethernet.begin(mac,ip) statement compiles properly in one program but not in another, the latter throws a compiler error in the Ethernet.begin statement stating that "Ethernet" has no declared type.
I've checked the keywords and KEYWORD1 lists "Ethernet" and KEYWORD2 lists "begin". Not sure what is going on. The compiler shows referencing the same library locations for both NativeEthernet and FNET for both programs. Does anyone have a clue as to how this can happen?

 

[TeensyWolf]

Have you tried QNEthernet? This is preferred over NativeEthernet

 

[CrazyDog]

Have you tried QNEthernet? This is preferred over NativeEthernet

NO. I haven't tried it because I haven't had any problems with Native Ethernet in applications except this recent odd behavior of the compiler.

 

[CrazyDog]

Problem solved. I started thinking about why compiler would post this error if it was accessing the same libraries in both program cases. So it occurred to me that this might be a scope problem in my code, so the compiler interpreted the function call as a prototype without any type declaration. Upon careful scrutiny I found a misplaced } which made a section of the code appear to not be in the setup() routine and thus out of scope.