Home >> All

•	bossa.link.* (5)	•	bossa.modules.* (11)	•	bossa.parser.* (1)	•	bossa.syntax.* (93)
•	bossa.util.* (9)

Package Samples:

• bossa.link
• bossa.modules
• bossa.parser
• bossa.syntax
• bossa.util

Classes:

• MethodDeclaration: Declaration of a method. Can be - a Nice method , with several method bodies @see bossa.syntax.MethodBodyDefinition - a Java method - an inlined method
• InlinedMethod: A method that is compiled by inlining code. The inlining class can be defined by the user. It keeps the core compiler small, while having very good efficiency. It has to be a subclass of gnu.mapping.Procedure , and should implement interface gnu.expr.Inlineable to be actually inlined.
• User: Messages for the user. When the error or warning is conditional, put it inside a 'if'. This is better than passing a boolean to error(), since the latter, forcing evaluation of the string, would slow down compilation.
• Macro: A macro. This interface should be implemented by classes that are used to implement inlined methods, and that need to do some semantic checking on their actual arguments.
• PackageExp: Temporary expression to represent a package or a package prefix. For instance, in java.lang.System.exit(0), java and java.lang is represented by a package exp.
• NiceFieldAccess: A field access in a Nice class. In terms of scoping, this is the symbol that is returned when the access to a field is done, either a 'get' or a 'set'.
• JavaClass: A class definition which reflects an existing native java class. This is usefull when you want to add type parameters to an existing java class.
• Alternative: Represents a method alternative in the link. It can be build either from information in a Bossa source, or read from a compiled bytecode file.
• FieldAccess: A field access. In terms of scoping, this is the symbol that is returned when the access to a field is done, either a 'get' or a 'set'.
• MethodContainer: An entity in which methods can be declared. It can have type parameters, that are implicitely added to the englobed methods.
• AbstractInterfaceImplementation: Declaration that an existing class implements an abstract interface. The abstract interface must belong to the current package.
• UserOperator: An operator whose semantics is defined by the user (i.e. not built-in). A contract can be attached to a user operator.
• TypeIdent: A syntactic type identifier. After scoping, it will either reveal to be a TypeConstructor or a MonotypeVar.
• CompiledContent: An abstract package source, where source or interface files and compiled code if applicable can be found.
• Content: An abstract package source, where source or interface files and compiled code if applicable can be found.
• SourceContent: An abstract package source, where source or interface files and compiled code if applicable can be found.
• LiteralArrayExp: Creates an array containing the given elements. The array type is infered as the minimal possible type.
• Expression: An expression of the Nice language. Subclasses of Expression have the 'Exp' suffix in their name.
• Definition: Abstract definition. May be a class definition, a method definition, an interface definition...
• RetypedJavaMethod: A Java method which is explicitely given a more precise type in the Nice source program.
• CompilationInterface: An abstract parent for Compilation. Allows methods to be in the Java style.
• MonotypeConstructor: A monotype, build by application of a type constructor to type parameters.
• Location: Represents a portion of the input file. Used to report errors to the user.

Home | Contact Us | Privacy Policy | Terms of Service