You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the options parsed by java_bytecode_language is required after the instance of this object has left scope. Under the current scheme, this option cannot be made available. Changes are required so that parsed options are available after the languaget instance has left scope.
The get_language_options method on languaget has no implementation, and is only overridden by java_bytecode_languaget. In the discussion on #691, it was suggested that
Option parsing from cmdlinet to optiont should be done with the rest of the parse_option code (in the application directory), not in the front-end.
I recommend that the get_language_options method be removed, and its contents from java_bytecode_language be moved to a more appropriate location in the parse_option code.
The text was updated successfully, but these errors were encountered:
This sounds like the right direction to go. The *_parse_option code should own the option object, populate it from cmdline and hold on to it for the duration of the program.
One of the options parsed by
java_bytecode_language
is required after the instance of this object has left scope. Under the current scheme, this option cannot be made available. Changes are required so that parsed options are available after thelanguaget
instance has left scope.The
get_language_options
method onlanguaget
has no implementation, and is only overridden byjava_bytecode_languaget
. In the discussion on #691, it was suggested thatI recommend that the
get_language_options
method be removed, and its contents fromjava_bytecode_language
be moved to a more appropriate location in the parse_option code.The text was updated successfully, but these errors were encountered: