1. meditor
An error report for mEdit...
If you run a program, and you change it's focus for any reason, when you close
it the editor window does not reappear, and won't unless you maximise it.
If there is an instance of the editor open already, and you open another for
editting... (c:\euphoria\bin\medit\editor.exe "<filename>" ) <-- How I have my
file associations set
then it opens a dialog window with:
"The instruction at 0041530d referenced memory at 00000000. The memory could not
be written"
This is on win2k, with the compiled version of the editor.
=======================
Patrick Barnes
Information Systems Group
201 Elizabeth St, Sydney
Patrick.Barnes at tg.nsw.gov.au
Ext: 91-3583
Ph:(02) 9284-3583
Mob: 0410 751 044
***********************************************************************
***********************************************************************
2. meditor
To whom ever maintains medit. The re-indent function has a bad bug with long
lines.
It breaks the statement lines characters beyond char 95 into little chunks on
the next several lines.
3. Re: meditor
- Posted by Pete Lomax <petelomax at blueyonder.co.uk>
Feb 06, 2005
-
Last edited Feb 07, 2005
George Walters wrote:
>To whom ever maintains medit. The re-indent function has a bad bug with long
>lines.
>It breaks the statement lines characters beyond char 95 into little chunks on
>the next several lines.
<slight digression; a related buglette>
When you select the Reformat option there is a prompt "Break lines at
column" which defaults to 94. Unfortunately, in format.ew there is a
constant colbreak=94 and getNumber(Break) is wrongly stored in a
variable called linebreak, which is actually a boolean, and is
initialised to 0 about 16 instructions after that store.
Obviously, "colbreak" should be a variable, set to getNumber(Break).
If that was fixed, you could use it to work round this, but besides
being a bit late, I don't think that is the point at all.
</digression>
Otherwise, the behaviour you describe is somewhat intentional....
Suppose you have:
mySequence =
{1,2,3,4,5,6,7,8,9,0,1,2,3,4,5,6,7,8,9,0,1,2,3,4,5,6,7,8,9,0,1,2,3,4,5,6,7,{8,9,0,1,2,3,4,5,6,7,8,9,0}}
(where the assignment is all on one line), it will output the {8, and
then 12 following digits, one per line, all "nicely" lined up under
the 8. It is the column alignment which is doing it.
If, however, you undo this change (you can always reverse the effects
of a Reformat by pressing Ctrl Z twice), and break the above line just
before the {8, then a Reformat will happily leave it alone.
In either case, the reformatted program will still run fine.
You might want to have a look at format.ew (while fixing the bug I
mentioned at the start) and suggest something, but I really don't
think there is anything possible, shy of a complete rewrite, and maybe
not even then.
Pete
