[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The parse error on the "x"
From: |
Andreas Weber |
Subject: |
Re: The parse error on the "x" |
Date: |
Sat, 02 Feb 2013 13:10:01 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 |
Am 02.02.2013 13:01, schrieb marco atzeri:
> Taban,
> try this way:
>
> function y = f (x,t)
> y = 5-2*x;
> endfunction
> first = 2;
...
Hi Marco, see my post.
I think his big problem was, that he made a script called dif.m and the
first line was "function y = f (x,t). He then gets a message:
warning: function name 'f' does not agree with function file name
'..../dif.m'
parse error near line 5 of file /home/andy/temp/Taban.m
syntax error
>>> first = 2;
But he only posted the last 2 lines here. As you know you can add a 1;
as first line to overcome this.
Regards, Andy
- Re: The parse error on the "x", (continued)
- Re: The parse error on the "x", Benjamin Abbott, 2013/02/01
- Re: The parse error on the "x", Taban, 2013/02/01
- Re: The parse error on the "x", Alec Teal, 2013/02/01
- Re: The parse error on the "x", Taban, 2013/02/02
- Re: The parse error on the "x", Andreas Weber, 2013/02/02
- Re: The parse error on the "x", Taban, 2013/02/02
- Re: The parse error on the "x", Andreas Weber, 2013/02/02
- Re: The parse error on the "x", Taban, 2013/02/02
- Re: The parse error on the "x", Andreas Weber, 2013/02/02
- Re: The parse error on the "x", marco atzeri, 2013/02/02
- Re: The parse error on the "x",
Andreas Weber <=
- Re: The parse error on the "x", marco atzeri, 2013/02/02
- Re: The parse error on the "x", Andreas Weber, 2013/02/02
- Re: The parse error on the "x", marco atzeri, 2013/02/02
- SOLVED was: The parse error on the "x", Andreas Weber, 2013/02/02
- Re: SOLVED was: The parse error on the "x", Taban, 2013/02/02
- Re: SOLVED was: The parse error on the "x", Andreas Weber, 2013/02/02
- Re: SOLVED was: The parse error on the "x", Taban, 2013/02/02
- Re: The parse error on the "x", Sergei Steshenko, 2013/02/02
- Re: The parse error on the "x", marco atzeri, 2013/02/02