eded".
> Any idea for that?
I think this is a dangerous direction of thought. Having a "terminator
if apparently needed" semantics of newline has already brought us the
inconsistency of if / else parsing inside and outside of blocks. No more
of that, please.
Best regards, Jan
--
+- J
t; Faculty of Bioscience Engineering
> Department of Mathematical Modelling, Statistics and Bio-Informatics
>
> tel : +32 9 264 59 87
> joris.m...@ugent.be
> ---
> Disclaimer : http://helpdesk.ugent.be/e-maildisclaimer.php
>
> [[alternative H
t (as the documentation
of fork demonstrates in an example, if I recall correctly).
Best regards, Jan
--
+- Jan T. Kim ---+
| email: [EMAIL PROTECTED] |
| WWW: http://www.cmp.uea.ac.
>From my rusty memory of X11 hacking, this should be elementary at
the X11 end of things -- something along the lines of adding key
event handling and responding to the Ctrl-W event.
There may be no need for this for X11, though, as the normal X11
way is to have the window manager manage such stuf
On Fri, Nov 20, 2020 at 02:48:11PM -0800, Bill Dunlap wrote:
> Perhaps the parser should warn if you use return() at all. It is rarely
> needed and is akin to the evil 'GOTO' statement in that it makes the flow
> of control less obvious to the reader.
My experience is contrary to this, using retu
