SourcFileOpsDoc.tioga
Created by Christian Jacobi, August 28, 1990 10:42:39 am PDT
Christian Jacobi, August 28, 1990 10:42:39 am PDT
Some basic feedback operations on source files.
Useful to hide the editor from some programming tools. This has been separated from both debugger and interpreter and reduced to functionality likely to be used by many tools.
For how to use it: Please read SourcFileOps.mesa. It is well documented.
However here is more documentation on why it is done this way.
--------------------------------
Date: Fri, 24 Aug 90 12:38:42 PDT
From: jacobi.pa
Subject: SourceFileOps for PCedar2.0
To: PCedarUsers^.pa
Cc: jacobi
Reply-to: Jacobi
SourceFileOps for PCedar2.0
Some basic feedback operations on source files.
Useful to hide the editor from some programming tools. This has been separated from both debugger and interpreter and reduced to functionality likely to be used by many tools.
Ripped out of Cirio, renamed, and, minor interface cleanup.
This is a small contribution to make that end of the world more comprehensible. The idea is to divide and conquer:
Cirio ought no more have a need to import and know viewers or tioga in its guts (of course the part building a tool needs it anyway...)
Other programming tools which pull some hair don't grab all of cirio with it (Unfortunatelly some tools need more than a single hair...)
Christian
--------------------------------
No message:
I have removed usage of viewer events. This simply wasn't justified. This removal was done without affecting any functionality. Except performance, which improved.
--------------------------------
Date: Tue, 28 Aug 90 07:45:55 PDT
From: Mike Spreitzer:PARC:Xerox
Subject: Re: SourceFileOps for PCedar2.0
In-reply-to: Originator: "jacobi:PA", UniqueString: "24-Aug-90 12:39:05 PDT"
To: Christian P Jacobi
Cc: Mike Spreitzer
(1) For C, we will need to deal in line numbers, not character indices.
(2) There's nothing a client of SourceFileOps can do with the REF ANY returned by OpenSource; how about not returning it?
(3) Why did you expand the set of selections to include secondary and nothing more? Why not make the set extensible (by, for example, using ATOMs, or a new opaque TYPE)?
--------------------------------
Subject: Re: SourceFileOps for PCedar2.0
In-reply-to: "Mike Spreitzer's message of Tue, 28 Aug 90 07:45:55 PDT"
To: Mike Spreitzer
Cc: Christian P Jacobi
For C, we will need to deal in line numbers
Make another package (or an extension) when it is necessary. (This functionality wasn't there before either).
nothing a client can do with the REF ANY
Pass it around, compare it, use WITH SELECT, put it on property lists. REF ANY because I do not want to import viewers into definition modules.
Why did you expand the set of selections to include secondary and nothing more
Why include secondary
So both procedures look like having the same kind of arguments
Why nothing more:
Because that is what I thought to be the intersection of what is easy to do now, and, what will stay easy in the next editor. (And because I'm not trying to extend everything, specially not before I see a need)
The main trust here is not perfection but separation. Once this functionality is out of the main thrust of cirio it can be improved separately, or, left out for sleep separately.
Christian
--------------------------------