For example you may create components in PowerBuilder, deploy it to Jaguar and use the proxies in PowerBuilder applications with no problems but six months in to the future you may want to web enable part of your application and you can run into problems when creating proxies/stubs for other deployment environments such as Java.

For example the following errors are generated by a PowerBuilder component that was deployed to EAServer and used in a PowerBuilder client application as a proxy without any problems but fails to compile as a Java stub:

D:\Jaguar CTS 3.0\html\classes\BAPS>javac *.java
_st_nc_dbe_bidyear.java:81: Identifier expected.
    public short new
                ^
_st_nc_ec_distbusent.java:81: Identifier expected.
    public short new
                ^
nc_dbe_bidyear.java:22: Identifier expected.
    short new
         ^
nc_ec_distbusent.java:22: Identifier expected.
    short new
         ^
4 errors

As we can see by the errors generated the problem was caused by a function called new in the PowerBuilder component. While new is not a reserved word in PowerBuilder it is in Java so the compiler throws it out.

Therefore as a guideline we always generate all of our components to all potential deployment environments to future proof any work and make sure we do not end up reworking the application due to other languages reserved words.