[Pharo-project] About SourcedMethodReference

Igor Stasenko siguctua at gmail.com
Wed Nov 10 21:44:07 CET 2010


On 10 November 2010 15:04, Johan Brichau <johan at inceptive.be> wrote:
>
> On 10 Nov 2010, at 12:14, Eliot Miranda wrote:
>
>> Why do you want to remove MethodReference?
>
> The work was initiated from Benjamin's work on a new browser for 'recent changes', which basically needs to manipulate source references.
>
> MethodReference is being used to this end in various parts of the system but it represents various different things: class comment reference, method source reference, class definition reference, etc.. In addition, it always represents a reference to the current source. To retrieve older versions of the source, you need to walk the changes stream yourself. Last but not least, various different tools are walking the changes file with different implementations.
>
> From that experience, the idea arose to create a sourcereference model that explicitly models the different source elements (methods, class comments, definitions, etc) and that has explicit timestamping. At the same time, we don't want to break existing tools and have embedded the exisiting MethodReference in that model.
>

+1

and please, keep in mind to delegate retrieving an actual source code
to some abstract layer.
So, then  we can bind any remote storage to it, like database or file
system whatever.

> Johan
>



-- 
Best regards,
Igor Stasenko AKA sig.




More information about the Pharo-project mailing list