Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330263

Summary:	[engine] No multiple dispatch when calling queries
Product:	[Modeling] Acceleo	Reporter:	Mikaël Barbero <mikael.barbero>
Component:	Core	Assignee:	Project Inbox <acceleo-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	laurent.goubet, mikael.barbero
Version:	3.0.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Mikaël Barbero

2010-11-15 11:47:24 EST

Hi guys,

I got a strange behavior. It seems that only the compile time type is taken into account when calling queries. It is a different behavior than the one with templates. Here is a sample:

[template public gen(e : EStructuralFeature)]
// [eType.q()/]
[if (eType.oclIsKindOf(EDataType))]
// [eType.oclAsType(EDataType).q()/] <-- MUST be the same as the first call to q(), but it is NOT.
[/if]

// --

// [eType.t()/]
[if (eType.oclIsKindOf(EDataType))]
// [eType.oclAsType(EDataType).t()/] <-- MUST be the same as the first call to t(), and it IS.
[/if]	
[/template]


[template public t(e : EDataType)]t(EDataType)[/template]
[template public t(e : EClass)]t(EClass)[/template]

[query public q(e : EDataType) : String =  'q(EDataType)' /]
[query public q(e : EClass) : String = 'q(EClass)' /]

Regards,
Mikael

Comment 1 Stephane Begaudeau

2011-06-24 09:12:43 EDT

This subject needs to be carefully analyzed, for example, can a call to a query be dispatched to a template if the template and the query can both be called?

Comment 2 Laurent Goubet

2016-03-29 05:51:56 EDT

A query and a template of the same name cannot be created ("module element already exists"), so this shouldn't be an issue.

However, dynamically dispatching to the proper query according to the argument's runtime type seems too major a change for a maintenance version. Should only be considered if we ever switch to Acceleo 4 (i.e. for a major version bump).