Re: Detecting the Eu version
Ferlin Scarborough wrote:
>
> Jason Gade wrote:
> >
> > Another way to handle it would be for the interpreter to defer all errors
> > until runtime.
> > A built-in version() function would work then the way people want it to.
> > But it might
> > make some kinds of bugs more difficult to find.
> >
> > The more we hash this out, the less relevant I think that it is. Derek
> > brought up
> > the point when he asked if he should use the [$] feature in win32lib or not.
> > How would
> > that work even with a good version statement? You either would have to
> > write parallel
> > code a la c type #ifdef or exit with a friendly message telling the user to
> > upgrade.
> >
> > It seems like we're dealing with two issues: Crashing in a way that the
> > user knows
> > it is a version error instead of trying to track down a syntax error, and
> > writing robust
> > libraries that work across different versions of the interpreter and are
> > able to take
> > advantage of new features.
> >
>
> I agree completely Jason. So, now I will make this my last message on this
> thread so that it can have a chance to die out. Seems like it has been done
> to death already.
>
> Later.
>
> Ferlin Scarborough
>
> Learn To Program Games in Free Courses At
> <a href="http://www.gameuniv.net">http://www.gameuniv.net</a>
>
> My Euphoria Home Page
> <a
> href="http://mywebpage.netscape.com/shadetreesoft">http://mywebpage.netscape.com/shadetreesoft</a>
>
Okay. Even though I wanted to kill this thread a few hours ago my interest is
piqued now that I see more nuance in it. How do other languages handle this
situation? Most of us know how C/C++ handles it (with #ifdef). What about
Python, Ruby, Lua, or Perl?
=====================================
Too many freaks, not enough circuses.
j.
|
Not Categorized, Please Help
|
|
