Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionis now a static delegateis now a static delegateis now a static delegateis now a static delegateis now a static delegateis now a static delegateis now a static delegateis now a static delegateis now a static delegateis now a static delegateinitialize TypeCheck3initialize TypeCheck3is now a static delegateTypeSymbul UND Expression: da ist was doppelt?not well-thought-out and unusedTypeSymbols are to be found in the corresponding subclasses, however, not every subclass will have a type symbolbad name, tends to be misused, s.a.
SymTypeExpressionFactory.createGenericsDeclaredType(TypeSymbol)hides surrogate usage, see other `createGenerics`-methodshides surrogate usage, see other `createGenerics`-methodshides surrogate usage, see other `createGenerics`-methodsarrays do not have a type symbol useSymTypeExpressionFactory.createTypeArray(SymTypeExpression, int)arrays do not have a name useSymTypeExpressionFactory.createTypeArray(SymTypeExpression, int)misused all the time, bad name; More often than not, one does not create a SymTypeExpression based solely on a symbol, consider either usingTypeCheck3.symTypeFromAST(de.monticore.types.mcbasictypes._ast.ASTMCType),WithinScopeBasicSymbolsResolver.resolveType(IBasicSymbolsScope, String), or any other method in this class.use TypeCheck to get SymTypeExpressions from MCTypes, this method is rather incorrect/incompletedid hide the usage of surrogate, and leads to questionable code consider usingWithinScopeBasicSymbolsResolver.resolveType(IBasicSymbolsScope, String), of creating a Surrogate explicitly (only if required)ALWAYS use TypeVarSymbols to create TypeVariablescreate a symbol and use it to create a SymTypeVariableSymTypeExpressionFactory.createTypeVariable(TypeVarSymbol)the other constructor is to be usedonly required for the deprecated type symboluse SymTypeExpressionFactory The Factory then uses the constructor belowuse SymtypeBoxingVisitorunused outside of tests, but not required for tests useNamesinstead, orgetTypeInfo().getName()same as the the other 2 methods even in spec? useSymTypeOfGenerics.getTypeConstructorFullName()same as the the other 2 methods even in spec? useSymTypeOfGenerics.getTypeConstructorFullName()use SymTypeUnboxingVisitorunused outside of tests, but not required for tests useNamesinstead, orgetTypeInfo().getName()questionable name: getter and setter do different things. one may add a getObjFullName() or similar if required also, seems unused in our main projectsunused in main projectsuse the Factory, the Factory uses the constructor belowuse SymTypeRelationsonly used in 1 test ONCE... in our main projectscannot assume fixed set for all languagesonly used in tests in our main projectsuse SymTypeRelationsleftover of old version, simply use deepEquals() instead.unused in main projects also: getter and setter do something different, questionable(should) return trueunused in main projectsis now a static delegateis now a static delegateis now a static delegatesimply use aTreeMapuse constrain* methods above.Use constrain* methods above.use constructorBuiltInTypeRelations()useLValueRelationsis now a static delegateis now a static delegate
-
Deprecated InterfacesInterfaceDescriptionuse
TypeCheck3useTypeCheck3useSymTypeRelationsuse MCCollectionSymTypeRelationsuse SymTypeRelationsuseTypeCheck3useLValueRelations
-
Deprecated ClassesClassDescriptionnot compatible with target typing, thus, this needs to be replaced with multiple CoCos, which do pass the target type if available. These CoCos have to be created for each non-terminal that contains an Expression. Please refer to the TypeCheck3 documentation and specifically
TypeCheck3.typeOf(ASTExpression, de.monticore.types.check.SymTypeExpression).to be replaced by typechecking Constants directly, no direct alternativesUseMCCommonStatementsSymTabCompletioninsteadUseMCVarDeclarationStatementsSymTabCompletioninsteadpart of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.part of typecheck1, useTypeCheck3instead.useTypeCheck3andSymTypeRelationsof no use anymore, ISynthesize/IDerive are deprecateduseSymTypeRelationsintegrated into MCCollectionSymTypesRelationsuseTypeCheck3
-
Deprecated Enum ClassesEnum ClassDescription
-
Deprecated FieldsFieldDescriptionUse
Grammar_WithConceptsAntlrLexer.VOCABULARYinstead.UseGrammar_WithConceptsAntlrParser.VOCABULARYinstead.UseSIUnitsAntlrLexer.VOCABULARYinstead.UseSIUnitsAntlrParser.VOCABULARYinstead.UseTagsAntlrLexer.VOCABULARYinstead.UseTagsAntlrParser.VOCABULARYinstead.UseODRulesAntlrLexer.VOCABULARYinstead.UseODRulesAntlrParser.VOCABULARYinstead.TypeSymbols are to be found in the corresponding subclasses, however, not every subclass will have a type symbolonly required for the deprecated type symbolcannot assume fixed set for all languages
-
Deprecated MethodsMethodDescriptionuse
SymTypeExpression2JavaConverter.getAsJavaType(SymTypeExpression)instead, which has a more descriptive name.is now a static delegateis now a static delegatepart of TypeCheck1. instead useSymTypeExpression.getSourceInfo().part of TypeCheck1. Not required in TypeCheck3.part of TypeCheck1. instead useSymTypeExpression.getSourceInfo().part of TypeCheck1. Not required in TypeCheck3.is now a static delegateis now a static delegateis now a static delegateis now a static delegatepart of TypeCheck1. instead useSymTypeExpression.getSourceInfo().part of TypeCheck1. Not required in TypeCheck3.is now a static delegateis now a static delegateis now a static delegateis now a static delegateinitialize TypeCheck3initialize TypeCheck3is now a static delegateuse TypeParameterRelationsuse TypeParameterRelationsnot well-thought-out and unusedbad name, tends to be misused, s.a.SymTypeExpressionFactory.createGenericsDeclaredType(TypeSymbol)hides surrogate usage, see other `createGenerics`-methodshides surrogate usage, see other `createGenerics`-methodshides surrogate usage, see other `createGenerics`-methodsarrays do not have a type symbol useSymTypeExpressionFactory.createTypeArray(SymTypeExpression, int)arrays do not have a name useSymTypeExpressionFactory.createTypeArray(SymTypeExpression, int)misused all the time, bad name; More often than not, one does not create a SymTypeExpression based solely on a symbol, consider either usingTypeCheck3.symTypeFromAST(de.monticore.types.mcbasictypes._ast.ASTMCType),WithinScopeBasicSymbolsResolver.resolveType(IBasicSymbolsScope, String), or any other method in this class.use TypeCheck to get SymTypeExpressions from MCTypes, this method is rather incorrect/incompletedid hide the usage of surrogate, and leads to questionable code consider usingWithinScopeBasicSymbolsResolver.resolveType(IBasicSymbolsScope, String), of creating a Surrogate explicitly (only if required)most current usages are wrong and have to be changed in the future! Currently considered to be removed, unless this functionality is required often enough (alternative: explicitly create a Surrogate and callSymTypeExpressionFactory.createTypeObject(TypeSymbol))ALWAYS use TypeVarSymbols to create TypeVariablescreate a symbol and use it to create a SymTypeVariableSymTypeExpressionFactory.createTypeVariable(TypeVarSymbol)use SymtypeBoxingVisitorunused outside of tests, but not required for tests useNamesinstead, orgetTypeInfo().getName()same as the the other 2 methods even in spec? useSymTypeOfGenerics.getTypeConstructorFullName()same as the the other 2 methods even in spec? useSymTypeOfGenerics.getTypeConstructorFullName()use SymTypeUnboxingVisitorunused outside of tests, but not required for tests useNamesinstead, orgetTypeInfo().getName()questionable name: getter and setter do different things. one may add a getObjFullName() or similar if required also, seems unused in our main projectsunused in main projectsuse SymTypeRelationsonly used in 1 test ONCE... in our main projectsonly used in tests in our main projectsuse SymTypeRelationsleftover of old version, simply use deepEquals() instead.unused in main projects also: getter and setter do something different, questionable(should) return trueunused in main projectspart of TypeCheck1. instead useSymTypeExpression.getSourceInfo().part of TypeCheck1. Not required in TypeCheck3.is now a static delegateis now a static delegateis now a static delegatedue to bad naming, use isMCCollectionsimply use aTreeMapuse constrain* methods above.Use constrain* methods above.do not use, only here until fix in grammardo not use, remove after fix of grammarsis now a static delegateis now a static delegate
-
Deprecated ConstructorsConstructorDescriptionuse the other Constructornew instances of a parser should be retrieved via a language's milluse default constructornew instances of a parser should be retrieved via a language's milluse default constructornew instances of a parser should be retrieved via a language's millnew instances of a parser should be retrieved via a language's millTypeSymbul UND Expression: da ist was doppelt?the other constructor is to be useduse SymTypeExpressionFactory The Factory then uses the constructor belowcontains no non-deprecated program logicuse the Factory, the Factory uses the constructor belowno logic that is not deprecated this is to be replaced by the default constructoruse constructor
BuiltInTypeRelations()