In Jacl scripting language, many scripts rely on the Jacl internal
representation of Lists to be space separated Strings.
The Jython scripting language, and most other language, does not have this
behavior. As a result, scripts need to be manually changed to reflect the
intended language independent behavior.
JACL: puts {This is a text message.} #relies on Jacl internals
JACL: puts "This is a text message."
==>
JYTHON: print ["This", "is", "a", "text", "message."] #incorrect
JYTHON: print "This is a text message."
The Jacl scripting language will dynamically convert any object
into a
String during printing, whereas the Jython scripting
language does not. Since the Jacl2Jython program does not determine nor track
runtime object types, you must manually review every
print statement
to ensure the runtime
String compatibility.
JACL: puts "myString=$myString"
JACL: puts "myNonString=$myNonString"
==>
JYTHON: print "myString="+myString
JYTHON: print "myNonString=" + 'myNonString' #manually modified