[Pharo-project] renggli mirror created on smalltalkhub
chaetal at gmail.com
Wed Jul 4 09:54:25 EDT 2012
> What can you do else than storing text?
I think of storing objects that represent operations I applied to my program: an ivar was renamed, a piece of code was extracted as a method, a method was moved to another class, etc. And those *live objects* can have a behavior that allows them to be applied to another program. This way I can think of applying other users' modifications to the code I've already modified: e.g., I've just renamed the same ivar (among other changes I don't want to loose), but the name my coworker invented was better and I want to apply that *particular* change.
In short, I would like to avoid treating source code as a text (which is just one possible way of representation) and keep it as live objects. Does it sound absolutely incapable?
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Wednesday, 4 July 2012 г. at 17:37, Camillo Bruni wrote:
> On 2012-07-04, at 15:30, Dennis Schetinin wrote:
> > On Wednesday, 4 July 2012 г. at 16:11, Damien Cassou wrote:
> > > On Wed, Jul 4, 2012 at 2:09 PM, Dennis Schetinin <chaetal at gmail.com (mailto:chaetal at gmail.com)> wrote:
> > > > Am I wrong considering migration to Git-or-AnythingElseTextOriented to be a
> > > > give up on hopes for a real object-oriented source control/management as it
> > > > could and should be in Smalltalk?
> > > >
> > >
> > >
> > >
> > > can you think of any feature we could have now we couldn't with Git?
> > I didn't say "now", I talked about "hopes". E.g. hopes for "Source" Control Tool being aware of refactorings and other *operations* I apply to my program, instead of treating it as a plain text with some changes of unknown nature. I'm not sure it's possible right now (I know it's not, better to say?). But with a Smalltalk-based source control we can have it on one splendid day in the future. And I think on the Git way we'll finish with just some advanced text-comparison algorithms. No?
> that has nothing to do with versioning per se.
> You can always hook in a different merger for git (that's already a built in feature)
> which simply redirects over a Pharo image and applies some more ST logic there.
> Going for something that is even more st specific is a waste of time IMO.
> What can you do else than storing text? ASTs? besides being incompatible
> with the whole world of text editable things you won't win much :/. Besides
> source code is quite a compact representation of ast's itself...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev