Re: INITIALLY clauses in loop

From: Peter Seibel (peter_at_javamonkey.com)
Date: 11/15/04 

Date: Mon, 15 Nov 2004 22:58:39 GMT

Kalle Olavi Niemitalo <kon@iki.fi> writes:

> Peter Seibel <peter@javamonkey.com> writes:
>
>> The new behavior seems right. From "6.1.1.6 Order of Execution":
>>
>> The following actions are exceptions to the linear order of
>> execution:
>
> Would it be reasonable to signal a STYLE-WARNING when the exceptions occur?

Uh, I don't think so. Because they *have* to appear out of order. That
is, INITALLY clauses, if any, have to appear textually before FOR
clauses, if any, at least according to the grammar in the LOOP
dictionary entry. Then 6.1.1.6 requires--as I read it--that the
variable initializations of the FOR clauses happen before the code in
the INITALLY clauses even though the stepping code corresponding to
the FOR clauses is obviously going to run after the code from the
INITIALLY clauses.

-Peter 

-- 
Peter Seibel                                      peter@javamonkey.com
         Lisp is the red pill. -- John Fraser, comp.lang.lisp

Relevant Pages

  • Re: multiple catch exceptions - MS feature request
    ... catch (TimeoutException, InvalidCastException, ..) ... SioComError = true; ... Note that if you have some common code for different types of exceptions, you can simplify the implementation a little in one of two ways: ... -- Refactor the code into a method shared by multiple catch clauses ...
    (microsoft.public.dotnet.languages.csharp)
  • [PATCH 2/2] namespace.pl : update file exclusion list
    ... The list of exceptions in kernel tree was out of date. ... the long list of if clauses to a hashes which is more efficient ...
    (Linux-Kernel)
  • Re: catching unmanaged exceptions in managed code, not working in release build
    ... you should place all catch clauses that catch unmanaged C++ ... types first before any catch clauses of managed types. ... After some testing I've found several problems: The exceptions are only ... release nor in the debug build the exceptions are catched. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Real life cost of using exceptions for control flow?
    ... I'm working with an app that uses exceptions for control flow. ... I would not worry about the cost of throwing/catching exception (although is ... because it is polluted by catch clauses that deal with the "normal" logic. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: INITIALLY clauses in loop
    ... >> clauses, if any, at least according to the grammar in the LOOP ... going to emit style warnings it would be for INITALLY clauses occuring ...
    (comp.lang.lisp)