On Tue 19 Mar, Nicholas Clark wrote: > > On Mon, Mar 18, 2002 at 11:33:16PM +0000, James Taylor wrote: > > > > On Mon 18 Mar, Geoff Youngs wrote: > > > > > > And the evaluator on dbl-click also makes sense. > > > > You might consider using the list context version though > > Or making select double click one context, and adjust the other
Or wrapping the loop in something that allows you to switch between the two at will. Hmmm, why don't I just do that now... <sound of frenetic typing> Oh, and I can allow multi line input... <more typing> Oh, and I can separate the user and main program namespaces... <more typing> Oh, and I can distinguish strings, numbers and undef values... <more typing> Hmmm, it started out neat, and now looks ugly. Why do I let these things get the better of me? I ought to just stop while I'm ahead. Oh well, new program attached. Usage is simple: Type some Perl code, multiple lines of it if you wish, and finish with a blank line. It will then report the return value. If your input consists of nothing more than the word 'scalar' or 'list' it will switch to that mode. Of course the debugger is much more flexible: perl -de 0 :-) PS. I apologise for the cuddled elses, some people don't like them (including Larry Wall et al) but my eyes find it hard to follow code where a solitary close brace can't be relied upon to be the end of a control structure. If you find any bugs or suboptimal bits, please let me know, I'm here to learn after all. -- James Taylor <[EMAIL PROTECTED]> Based in Southam, Cheltenham, UK. PGP key available ID: 3FBE1BF9 Fingerprint: F19D803624ED6FE8 370045159F66FD02
EvalLoop,102
Description: application/riscos
