Recent changes to tickets

#2 Shell_Execute variant without result

Gautier de Montmollin — Sat, 28 Nov 2020 16:49:08 -0000

Done in commit #286.

#2 Shell_Execute variant without result

Gautier de Montmollin — Sat, 28 Nov 2020 16:48:54 -0000

status: open --> closed

#3 Result parameter for Create, Append, Open, Close

Gautier de Montmollin — Fri, 27 Nov 2020 20:58:49 -0000

Description has changed:

Diff:

--- old
+++ new
@@ -1,4 +1,4 @@
-Since exception handling is not yet supported, we&#39;d like a mean to handle cases where the above file operations fail.
+Since exception handling is not yet supported, we&#39;d like a mean to handle cases where the file operations Create, Append, Open, Close fail. An idea is to have variants with a Result parameter. These variants can be useful too when exception handling is implemented, by the way.
 Example for Create:
 ~~~
   --  If the operation fails, one of the Name_Error, Use_Error, Status_Error exceptions is raised.

#3 Result parameter for Create, Append, Open, Close

Gautier de Montmollin — Fri, 27 Nov 2020 20:54:45 -0000

Description has changed:

Diff:

--- old
+++ new
@@ -1,4 +1,4 @@
-Since exception handling is not yet supported, we&#39;d like a mean to handle case where the above file operations fail.
+Since exception handling is not yet supported, we&#39;d like a mean to handle cases where the above file operations fail.
 Example for Create:
 ~~~
   --  If the operation fails, one of the Name_Error, Use_Error, Status_Error exceptions is raised.

Result parameter for Create, Append, Open, Close

Gautier de Montmollin — Fri, 27 Nov 2020 20:51:16 -0000

Since exception handling is not yet supported, we'd like a mean to handle case where the above file operations fail.
Example for Create:

  --  If the operation fails, one of the Name_Error, Use_Error, Status_Error exceptions is raised.

  procedure Create (File : in out File_Type; Name : String);
  procedure Create (File : in out File_Type; Name : VString);

  --  Variants of Create, Append, Open, Close with a "Result" parameter.
  --  If the operation fails, Result is set to the value corresponding to the exception.

  type File_Operation_Result is (Success, Erroneous_Name, Erroneous_Use, Erroneous_Status);

  procedure Create (File : in out File_Type; Name : String; Result: out File_Operation_Result);
  procedure Create (File : in out File_Type; Name : VString; Result: out File_Operation_Result);

Result parameter for Create, Append, Open, Close

Gautier de Montmollin — Fri, 27 Nov 2020 20:51:16 -0000

Ticket 3 has been modified: Result parameter for Create, Append, Open, Close
Edited By: Gautier de Montmollin (gdemont)
Description updated:
--- description-old

+++ description-new

@@ -1,4 +1,4 @@

-Since exception handling is not yet supported, we'd like a mean to handle case where the above file operations fail.
+Since exception handling is not yet supported, we'd like a mean to handle cases where the above file operations fail.
Example for Create:
~~~
-- If the operation fails, one of the Name_Error, Use_Error, Status_Error exceptions is raised.

Result parameter for Create, Append, Open, Close

Gautier de Montmollin — Fri, 27 Nov 2020 20:51:16 -0000

Ticket 3 has been modified: Result parameter for Create, Append, Open, Close
Edited By: Gautier de Montmollin (gdemont)
Description updated:
--- description-old

+++ description-new

@@ -1,4 +1,4 @@

-Since exception handling is not yet supported, we'd like a mean to handle cases where the above file operations fail.
+Since exception handling is not yet supported, we'd like a mean to handle cases where the file operations Create, Append, Open, Close fail. An idea is to have variants with a Result parameter. These variants can be useful too when exception handling is implemented, by the way.
Example for Create:
~~~
-- If the operation fails, one of the Name_Error, Use_Error, Status_Error exceptions is raised.

Shell_Execute variant without result

Gautier de Montmollin — Fri, 27 Nov 2020 20:40:07 -0000

Often, the result value of Shell_Execute is not useful, so an idea is to turn Shell_Execute into the following procedures. In HAC_Pack's specification:

  procedure Shell_Execute (Command : String; Result : out Integer);
  procedure Shell_Execute (Command : VString; Result : out Integer);

  --  In this version, the result value is discarded:
  procedure Shell_Execute (Command : String);
  procedure Shell_Execute (Command : VString);

Shell_Execute variant without result

Gautier de Montmollin — Fri, 27 Nov 2020 20:40:07 -0000

Ticket 2 has been modified: Shell_Execute variant without result
Edited By: Gautier de Montmollin (gdemont)
Status updated: u'open' => u'closed'

#1 Block - Declare begin end

Gautier de Montmollin — Mon, 25 Mar 2019 01:11:10 -0000

There is definitely something wrong in the implementation of the block statement, see comments @ procedure Block_statement in HAC.Parser. Perhaps I should just stop the compilation on block statements, and revive this construct when I find a correct way of handling the stack. A hint in those comments points to the FOR statement which has an implicit DECLARE.

I have disabled the support for block statements (rev. 81).
Better that than having an erroneous compilation...