Bresticker, Shalom wrote: > I am not sure there is a need to declare a task input argument as > automatic, since input arguments are initialized on entrance to the task > anyway, by being written to by the value of the actual argument. Recursion > > However, it might make sense for output arguments to be automatic. > > Shalom > > >> According to the 1800 LRM (section 12.2), we can now have >> automatic formal arguments for static tasks (and vice versa). >> However, I could not discover the "official" syntax to do so >> in the LRM. >> >> (1) >> >> The most obvious one: >> >> task mytask (input automatic reg d); >> Whis is wrong as per BNF. >> >> (2) >> >> If I go to non ansi-style: >> >> task mytask (input d); >> automatic reg d; >> endtask >> Then some tool is giving redeclaration error for 'd', which >> is correct as per mantis 1169. >> >> (3) >> >> Finally, if I try: >> >> task mytask; >> input d; >> automatic reg d; >> >> Then, it is okay as per BNF. However, if I try to make it >> implicit data type, then is wrong as per BNF. >> >> task mytask; >> input d; >> automatic d; >> >> What is the correct way to achieve the behaviour? >> >> -- >> Regards >> Surya >> >> >> >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> > --------------------------------------------------------------------- > Intel Israel (74) Limited > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Dec 18 13:06:05 2007
This archive was generated by hypermail 2.1.8 : Tue Dec 18 2007 - 13:07:39 PST