Community
Participate
Working Groups
Build Identifier: Xtext 2.0.0.v201105230203 xtend2: def dispatch compile(InterfaceDcl src) { val params = [ParameterDcls pd|if (pd!= null)'''«FOR p : pd.paramDcl SEPARATOR ', '»«p.paramType» «p.name»«ENDFOR»'''] val xtends = [List<InterfaceDcl> idcl|if (!idcl.empty) ''' extends «FOR i : idcl SEPARATOR ', '»«i.nameWithVersion»«ENDFOR»'''] ''' // Interface definitions java: protected CharSequence _compile(final OpDcl opDcl) { StringConcatenation _xblockexpression = null; { final Function1<ParameterDcls,StringConcatenation> _function = new Function1<ParameterDcls,StringConcatenation>() { public StringConcatenation apply(final ParameterDcls pd) { StringConcatenation _xifexpression = null; boolean _operator_notEquals = ObjectExtensions.operator_notEquals(pd, null); if (_operator_notEquals) { StringConcatenation _builder = new StringConcatenation(); { EList<ParamDcl> _paramDcl = pd.getParamDcl(); boolean hasAnyElements = false; for(ParamDcl p : _paramDcl) { if (!hasAnyElements) { hasAnyElements = true; } else { _builder.appendImmediate(", ", ""); } => null _paramType = Idl2IcmCompiler.this.getParamType(p); _builder.append(_paramType, ""); _builder.append(" "); Reproducible: Always Steps to Reproduce: 1. bug is marked as => 2. 3.
workaround: def dispatch compile(InterfaceDcl src) { val params = [ParameterDcls pd|if (pd!= null)'''«FOR p : pd.paramDcl SEPARATOR ', '»«p.paramType.toString» «p.name»«ENDFOR»'''] val xtends = [List<InterfaceDcl> idcl|if (!idcl.empty) ''' extends «FOR i : idcl SEPARATOR ', '»«i.nameWithVersion»«ENDFOR»'''] und: def StringConcatenation getParamType(ParamDcl paramDcl) { if (paramDcl != null && paramDcl.typeSpec != null) paramDcl.typeSpec.toTypeDeclaration else '''''' }
Is this one still reproducable?
(In reply to comment #2) > Is this one still reproducable? I mean with Xtext 2.0.1
(In reply to comment #3) > (In reply to comment #2) > > Is this one still reproducable? > > I mean with Xtext 2.0.1 good question ;-) I did not retest it because I've implemented a workaround to avoid this... Unfortunately my code changed a lot and I cannot rollback to the point where this issue happened. sorry, serano
closing this unless someone is able reproduce it.
Closing all bugs that were set to RESOLVED before Neon.0