ANN: make-doc-pro-104 RC1
[1/7] from: robert::muench::robertmuench::de at: 19-Jul-2002 19:38
Hi, I'm now playing being a big software company ;-)) with beta, RC etc.
release cycles. Anyway, I have updated MDP and fixed quite some bugs for
special cases that are not so special if you let a non programmer use
MDP ;-)). Further I'm thinking about changing the history section.
Therefor I have changed the HTML emitter of bug-reporter to produce a
complete list. Now you can see what bugs are open, fixed etc. Let me
know what you think about this.
Well, than have a lot of fun with MDP. Hopefully more and more people
will use it... If you find any bugs etc. let me know. I haven't written
a web-interface to submit bugs into my bug-database (yet).
As always you can access the actual version through my Rebsite or by
directly downloading here: http://www.robertmuench.de/make-doc-pro.r and
don't forget to have a look at my homepage ;-)). Robert
[2/7] from: anton:lexicon at: 20-Jul-2002 17:57
You've ~still~ got those halt statements in there.
===What to do about halt statements...
Anton.
[3/7] from: robert:muench:robertmuench at: 20-Jul-2002 18:59
> -----Original Message-----
> From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]
<<quoted lines omitted: 3>>
> Subject: [REBOL] Re: ANN: make-doc-pro-104 RC1
> You've ~still~ got those halt statements in there.
Hi, ups really? Shouldn't be the case... I scan through the code. Well,
there are only two of them in the last two lines. Just delete the last
one and keep the one for debug-mode. That's it. Robert
[4/7] from: anton:lexicon at: 21-Jul-2002 17:09
But as I've said before, I don't want to be
doing this everytime you make a new release.
It will cause me to... either make a script to
remove it automatically, which I view as not
a perfect solution, or not to stay up-to-date
with your changes, which is also not a perfect
solution. You are losing potential feedback
from me, here.
Can you explain why you really need to halt
the script "unnaturally" like this?
:)
Anton.
[5/7] from: robert:muench:robertmuench at: 21-Jul-2002 18:05
> -----Original Message-----
> From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]
<<quoted lines omitted: 4>>
> But as I've said before, I don't want to be
> doing this everytime you make a new release.
It's not a release yet ;-)).
> Can you explain why you really need to halt
> the script "unnaturally" like this? :)
Because falling back to the command-line of Rebol is way faster when I
need to start MDP over and over again. It keeps the last directory and
selected file information, that's why I end to the command-line. Robert
[6/7] from: anton:lexicon at: 22-Jul-2002 3:21
> It's not a release yet ;-)).
Well then, I can't wait for a release!
:0
It's ok. ;)
> > Can you explain why you really need to halt
> > the script "unnaturally" like this? :)
>
> Because falling back to the command-line of Rebol is way faster when I
> need to start MDP over and over again. It keeps the last directory and
> selected file information, that's why I end to the command-line. Robert
Do you mean to say you change the current dir?
That is very naughty.
If, for whatever reason, your script fails before restoring
the current directory, you will have modified the environment.
It seems that every man and his dog has made a recursive directory
parser (ie. tree).
I have made one, but it does not modify the current directory.
This is excellent, because my code may fail. If not today,
then maybe in future, when a new version of rebol is out.
I want to make my code resistant to annoying little things
like that. This feature also made it easier to develop.
(Of course, we can always wrap possible-crashing code in a
try block.)
Regards,
Anton.
[7/7] from: robert:muench:robertmuench at: 22-Jul-2002 9:16
> -----Original Message-----
> From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]
<<quoted lines omitted: 4>>
> Do you mean to say you change the current dir?
> That is very naughty.
No, I don't. It's just request-file storing the informatio about the
last accessed directory. Not make-doc-pro. There is still a bug in the
=include command as it only scans in the directory make-doc-pro was
started in. So you see... I don't change directories. I will scan
different directories for the =include statement but don't change the
internal state.
> I want to make my code resistant to
> annoying little things like that. This feature also made it
> easier to develop. (Of course, we can always wrap
> possible-crashing code in a try block.)
Right. MDP could perhaps be made a bit safer in some hot-spots. Mostly
it accepts everything you throw at it but will perhaps generate wrong
looking output. Robert
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted