1. Automatic Removal???
Well! Being automagically removed from the mailing list was a supprise! I
had begun to wonder why I wasn't recieving any posts recently. Although,
now that
I have resubscribed, I imagine that it will happen again. My ISP is a
local BBS,
and has been undergoing restructuring. While I was still able to use the Web
and other services, their IP had changed but the Internic hadn't updated, so I
couldn't recieve e-mail. Naturally, by the time everything was working
again, I
had missed 80 some posts in 6 days (geez, pretty active!). Anyway, to make a
long story short, I am in the midst of changing to a full-fleged ISP,
however I
plan to keep my email at DJO (barring another fiasco like this recent one).
Anyway, down the Euphoria stuff. Work still continues on UnShroud, but has
hit
some pretty good size hurdles (#1 being finals at school). Like Robert Craig
said in a previous post regarding unshrouding, Shroud.ex does a VERY thorough
job of ripping out program information. Unshrouding is a darned difficult
thing
to do. While resolving internal Euphoria procedure and function calls is a
straitforward process, trying to give names to external routines is a
pointless
task. This leads to a very dry, computer generated look for the unshrouded
file.
While easier to read, it is still shrouded in nearly every sense of the word.
Anyway, once I get UnShroud working to the point where it can unshroud
itself into
a decent, readable form (that will still be able to be run by EUPHORIA) I will
release it.
I have also thought about the Interpret() function, and have come to the
conclusion that it just might be easier to come up with a *very* reduced
language
(perhaps a simple BASIC) that could be interpreted by an Interpret.e (to keep
from having to change parts of EUPHORIA, as Robert said would probably have
to be
done). So how about some MINIMAL functionality ideas (that's MINIMAL
requirements, not "Hey, I think this would be cool/neat/etc). Obviously,
for a first attempt, only a single line or two need be processed, so
variables and
+ - * \ ^ support need be included. Once that works, control routines such as
IF-THEN and FOR-NEXT can be added. After that point, I'm not sure. But there
needs to be an Official code base that everyone would work from, with any
enhancements being only personal in nature, or submitted for
review\revision by the developement team, etc. Any and all ideas about
putting this together are
welcomed.
That's all for tonight,
James Powell
