incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henry Story <henry.st...@bblfish.net>
Subject Re: [jira] [Updated] (CLEREZZA-599) EzMGraph imports too many implicits
Date Mon, 11 Jul 2011 07:47:55 GMT
I am not sure how your proposal relates to EzMGraph importing too many 
implicits. Do the renamings remove the problem of having methods
appear that have no relation to the class?

It seems like  you should open a new issue for renaming the Preamble.

On 9 Jul 2011, at 12:47, Reto Bachmann-Gmür wrote:

> I think they should stay there, so one just has to import one out of
> preamble-object, preamble-instance or ezmgraph.


> 
> I thin preamble could be renamed to EzGraph to make the three level more
> clear.
> EzGraph: object the utilities that do nor depend on a particular tc
> EzGraph class: the utilities that require a specified readable tc
> EzMGraph: the utilities that require a readwrite tc
> On Jul 9, 2011 12:37 PM, "Henry Story (JIRA)" <jira@apache.org> wrote:
>> 
>> [
> https://issues.apache.org/jira/browse/CLEREZZA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>> 
>> Henry Story updated CLEREZZA-599:
>> ---------------------------------
>> 
>> Attachment: before-tooManyMethods.png
>> 
>> Here one sees a number of methods on the EzGraph instance that really have
> no role in that class:
>> - bigint2lit
>> - bool2lit
>> - date2lit
>> - double2lit
>> 
>> and many more not shown on that screenshot
>> 
>>> EzMGraph imports too many implicits
>>> -----------------------------------
>>> 
>>> Key: CLEREZZA-599
>>> URL: https://issues.apache.org/jira/browse/CLEREZZA-599
>>> Project: Clerezza
>>> Issue Type: Improvement
>>> Reporter: Henry Story
>>> Attachments: before-tooManyMethods.png
>>> 
>>> 
>>> Importing all the implicit Preamble methods into EzMGraph is both
> unnecessary and problematic of working with that class with IDEs. As shown
> in the attached screenshots, IDEs will show - and should show - implicit
> methods just like any other methods. Extending a class therefore with
> implicit methods that convert between very different types, is not the right
> solution, both in OO programming and in pragmatic usage.
>> 
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>> 
>> 

Social Web Architect
http://bblfish.net/


Mime
View raw message