$ARGS$ seems to be broken

$ARGS$ macro seems to be broken. None of these insert anything into the editor:

I have reported this issue on Saturday. Hope that a fix it for it will be available soon.

Thank you very much.

Please see http://www.softtreetech.com/support/phpBB2/viewtopic.php?t=23812

Well, something definitely has changed, but $ARGS$ now displays extremely weird behavior. I've created the following function:

	Code:
	CREATE FUNCTION dbo.fs_test_function ( @first_argument INT ,@second_argument VARCHAR(64) ,@third_argument BIGINT ,@fourth_argument BIT ) RETURNS INT AS BEGIN RETURN 0 END GO

And the following snippets (with the following results):
Snippet1:

	Code:
	args: -- comment $ARGS$ -- another comment args_end:

Result1:

	Code:
	args: -- comment @first_argument, @second_argument, @third_argument, @fourth_argument -- another comment args_end:

Snippet2:

	Code:
	args_type_classes: -- comment $ARGS(type_classes)$ -- another comment args_type_classes_end:

Result2:

	Code:
	args_type_classes: -- comment @first_argument int, @second_argument varchar, @third_argument bigint, @fourth_argument bit -- an another comment args_type_classes_end:

Snippet3:

	Code:
	args_types: -- comment $ARGS(types)$ -- another comment args_types_end:

Result3:

	Code:
	args_types: -- comment @first_argument int, @second_argument varchar(64), @third_argument bigint, @fourth_argument bit -- another comment nt args_types_end:

Snippet4:

	Code:
	args_vertical: -- comment $ARGS(vertical)$ -- another comment args_vertical_end:

Result4:

	Code:
	args_vertical: -- comment @first_argument, @second_argument, @third_argument, @fourth_argument -- another cor comment args_vertical_end:

Snippet5:

	Code:
	args_vertical_type_classes: -- comment $ARGS(vertical,type_classes)$ -- another comment args_vertical_type_classes_end:

Result5:

	Code:
	args_vertical_type_classes: -- comment @first_argument, @second_argument, @third_argument, @fourth_argument -- another comment args_vertical_type_classes_end:

Are there any changes in DB Queries that could be the cause of this?

Thank you for your continues and valuable feedback. We have sent you a link for the private build 6.3.170. Please let us know if this issue has been fixed in that build and the $ARGS$ is working correctly in that build.

Yes, it is, thank you very much for the quick fix.