[Oorexx-rfes] [ oorexx-Feature Requests-1802613 ] Add an invalid argument major message code.

[SourceForge.net <noreply@so...>]

Feature Requests item #1802613, was opened at 2007-09-26 06:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Error Codes
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Rick McGuire (bigrixx)
Assigned to: Rick McGuire (bigrixx)
Summary: Add an invalid argument major message code.

Initial Comment:
A lot of error checking needs to make the decision between using error 40 for invalid call to routine vs error 93 for invalid call to method.  This can be somewhat confusing, as functions are sometimes just passthroughs to methods, messages generally refer to argument position, which can shift when function calls are converted to method calls and the methods perform the argument checks.  

It would be more convenient if there was a major error code for 'Invalid argument', with subcodes for the different common error conditions for arguments.  All references to specific arguments should be by name, not by ordinal position. 

It's not necessary that existing messages be converted over to these new errors, but it would be a good idea to start adding the new messages so they can be used for new development.  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

[Oorexx-rfes] [ oorexx-Feature Requests-1802613 ] Add an invalid argument major message code.

[SourceForge.net <noreply@so...>]

Feature Requests item #1802613, was opened at 2007-09-26 06:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Error Codes
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Rick McGuire (bigrixx)
Assigned to: Rick McGuire (bigrixx)
Summary: Add an invalid argument major message code.

Initial Comment:
A lot of error checking needs to make the decision between using error 40 for invalid call to routine vs error 93 for invalid call to method.  This can be somewhat confusing, as functions are sometimes just passthroughs to methods, messages generally refer to argument position, which can shift when function calls are converted to method calls and the methods perform the argument checks.  

It would be more convenient if there was a major error code for 'Invalid argument', with subcodes for the different common error conditions for arguments.  All references to specific arguments should be by name, not by ordinal position. 

It's not necessary that existing messages be converted over to these new errors, but it would be a good idea to start adding the new messages so they can be used for new development.  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

[Oorexx-rfes] [ oorexx-Feature Requests-1802613 ] Add an invalid argument major message code.

[SourceForge.net <noreply@so...>]

Feature Requests item #1802613, was opened at 2007-09-26 06:31
Message generated for change (Comment added) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Error Codes
>Group: Next Release
>Status: Pending
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Rick McGuire (bigrixx)
Assigned to: Rick McGuire (bigrixx)
Summary: Add an invalid argument major message code.

Initial Comment:
A lot of error checking needs to make the decision between using error 40 for invalid call to routine vs error 93 for invalid call to method.  This can be somewhat confusing, as functions are sometimes just passthroughs to methods, messages generally refer to argument position, which can shift when function calls are converted to method calls and the methods perform the argument checks.  

It would be more convenient if there was a major error code for 'Invalid argument', with subcodes for the different common error conditions for arguments.  All references to specific arguments should be by name, not by ordinal position. 

It's not necessary that existing messages be converted over to these new errors, but it would be a good idea to start adding the new messages so they can be used for new development.  

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2007-09-27 08:51

Message:
Logged In: YES 
user_id=1125291
Originator: YES

This added a new 88 major code, plus a bunch of minor codes for common
argument validation conditions.  The messages in this category are
restricted to problems with specific arguments.  So no minimum
argument/maximum argument messages, but there is a required argument
message.  There's the standard user message, plus a general message where
the substitutions are the argument name and the reason it was bad. 

Over time, the intent will be to replace a lot of Error 40 and Error 93
messages issued by the interpreter with these new ones.  When this is done,
the arguments will be flagged by the documented argument name, not position
number. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

[Oorexx-rfes] [ oorexx-Feature Requests-1802613 ] Add an invalid argument major message code.

[SourceForge.net <noreply@so...>]

Feature Requests item #1802613, was opened at 2007-09-26 06:31
Message generated for change (Settings changed) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Error Codes
>Group: v3.2.0
>Status: Open
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Rick McGuire (bigrixx)
Assigned to: Rick McGuire (bigrixx)
Summary: Add an invalid argument major message code.

Initial Comment:
A lot of error checking needs to make the decision between using error 40 for invalid call to routine vs error 93 for invalid call to method.  This can be somewhat confusing, as functions are sometimes just passthroughs to methods, messages generally refer to argument position, which can shift when function calls are converted to method calls and the methods perform the argument checks.  

It would be more convenient if there was a major error code for 'Invalid argument', with subcodes for the different common error conditions for arguments.  All references to specific arguments should be by name, not by ordinal position. 

It's not necessary that existing messages be converted over to these new errors, but it would be a good idea to start adding the new messages so they can be used for new development.  

----------------------------------------------------------------------

Comment By: Rick McGuire (bigrixx)
Date: 2007-09-27 08:51

Message:
Logged In: YES 
user_id=1125291
Originator: YES

This added a new 88 major code, plus a bunch of minor codes for common
argument validation conditions.  The messages in this category are
restricted to problems with specific arguments.  So no minimum
argument/maximum argument messages, but there is a required argument
message.  There's the standard user message, plus a general message where
the substitutions are the argument name and the reason it was bad. 

Over time, the intent will be to replace a lot of Error 40 and Error 93
messages issued by the interpreter with these new ones.  When this is done,
the arguments will be flagged by the documented argument name, not position
number. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

[Oorexx-rfes] [ oorexx-Feature Requests-1802613 ] Add an invalid argument major message code.

[SourceForge.net <noreply@so...>]

Feature Requests item #1802613, was opened at 2007-09-26 06:31
Message generated for change (Settings changed) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Error Codes
Group: v3.2.0
>Status: Pending
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Rick McGuire (bigrixx)
Assigned to: Rick McGuire (bigrixx)
Summary: Add an invalid argument major message code.

Initial Comment:
A lot of error checking needs to make the decision between using error 40 for invalid call to routine vs error 93 for invalid call to method.  This can be somewhat confusing, as functions are sometimes just passthroughs to methods, messages generally refer to argument position, which can shift when function calls are converted to method calls and the methods perform the argument checks.  

It would be more convenient if there was a major error code for 'Invalid argument', with subcodes for the different common error conditions for arguments.  All references to specific arguments should be by name, not by ordinal position. 

It's not necessary that existing messages be converted over to these new errors, but it would be a good idea to start adding the new messages so they can be used for new development.  

----------------------------------------------------------------------

Comment By: Rick McGuire (bigrixx)
Date: 2007-09-27 08:51

Message:
Logged In: YES 
user_id=1125291
Originator: YES

This added a new 88 major code, plus a bunch of minor codes for common
argument validation conditions.  The messages in this category are
restricted to problems with specific arguments.  So no minimum
argument/maximum argument messages, but there is a required argument
message.  There's the standard user message, plus a general message where
the substitutions are the argument name and the reason it was bad. 

Over time, the intent will be to replace a lot of Error 40 and Error 93
messages issued by the interpreter with these new ones.  When this is done,
the arguments will be flagged by the documented argument name, not position
number. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

[Oorexx-rfes] [ oorexx-Feature Requests-1802613 ] Add an invalid argument major message code.

[SourceForge.net <noreply@so...>]

Feature Requests item #1802613, was opened at 2007-09-26 05:31
Message generated for change (Settings changed) made by wdashley
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Error Codes
Group: v3.2.0
>Status: Closed
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Rick McGuire (bigrixx)
Assigned to: Rick McGuire (bigrixx)
Summary: Add an invalid argument major message code.

Initial Comment:
A lot of error checking needs to make the decision between using error 40 for invalid call to routine vs error 93 for invalid call to method.  This can be somewhat confusing, as functions are sometimes just passthroughs to methods, messages generally refer to argument position, which can shift when function calls are converted to method calls and the methods perform the argument checks.  

It would be more convenient if there was a major error code for 'Invalid argument', with subcodes for the different common error conditions for arguments.  All references to specific arguments should be by name, not by ordinal position. 

It's not necessary that existing messages be converted over to these new errors, but it would be a good idea to start adding the new messages so they can be used for new development.  

----------------------------------------------------------------------

Comment By: Rick McGuire (bigrixx)
Date: 2007-09-27 07:51

Message:
Logged In: YES 
user_id=1125291
Originator: YES

This added a new 88 major code, plus a bunch of minor codes for common
argument validation conditions.  The messages in this category are
restricted to problems with specific arguments.  So no minimum
argument/maximum argument messages, but there is a required argument
message.  There's the standard user message, plus a general message where
the substitutions are the argument name and the reason it was bad. 

Over time, the intent will be to replace a lot of Error 40 and Error 93
messages issued by the interpreter with these new ones.  When this is done,
the arguments will be flagged by the documented argument name, not position
number. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1802613&group_id=119701