User talk:Kri: Difference between revisions

862 bytes added ,  21 September 2014
→‎repmat different syntax: Where should it be mentioned in that case?
m (→‎repmat different syntax: signing previous comment)
(→‎repmat different syntax: Where should it be mentioned in that case?)
Line 4: Line 4:


: Yes, that seems to be what I meant, thank you for linking to the bug report. When I wrote that the syntax is different, I meant that the syntax differed for ''some'' case. I don't think the syntax should differ from that in Matlab in ''any'' case. But why did you remove the note about making sure Octave is compatible with Matlab and vice versa, don't you think that is worth mentioning?  —[[User:Kri|Kri]] ([[User talk:Kri|talk]]) 05:04, 21 September 2014 (PDT)
: Yes, that seems to be what I meant, thank you for linking to the bug report. When I wrote that the syntax is different, I meant that the syntax differed for ''some'' case. I don't think the syntax should differ from that in Matlab in ''any'' case. But why did you remove the note about making sure Octave is compatible with Matlab and vice versa, don't you think that is worth mentioning?  —[[User:Kri|Kri]] ([[User talk:Kri|talk]]) 05:04, 21 September 2014 (PDT)
:: I don't think it's worth mentioning on the list of project as it is not a project, just like we do not make reference of the Octave coding standards there. It wouldn't be the right place for it. And even if it was, I disagree with that opinion and considering the amount of Octave features missing from Matlab, I would say that so do most of Octave developers. One should be careful to not implement something that could clash with exiting Matlab functionality but its' perfectly fine to implement things that are missing in Matlab. --[[User:Carandraug|carandraug]] ([[User talk:Carandraug|talk]]) 07:51, 21 September 2014 (PDT)
:: I don't think it's worth mentioning on the list of project as it is not a project, just like we do not make reference of the Octave coding standards there. It wouldn't be the right place for it. And even if it was, I disagree with that opinion and considering the amount of Octave features missing from Matlab, I would say that so do most of Octave developers. One should be careful to not implement something that could clash with exiting Matlab functionality but its' perfectly fine to implement things that are missing in Matlab. --[[User:Carandraug|carandraug]] ([[User talk:Carandraug|talk]]) 07:51, 21 September 2014 (PDT)
:::Okay, that makes sense. In this case however, Octave and Matlab can both repeat arrays in more than two dimensions, but require different syntaxes for doing so. So when Octave eventually will support the syntax used in Matlab, it will support two different syntaxes for doing the same thing, which is not necessarily a good thing. It would probably have been better if the syntax used in Matlab had been implemented from the beginning. Do you agree with me?
:::In that case maybe we should say something about that to the Octave developers. Where do you think it could be mentioned in that case?
:::Or did Octave implement that function before it was implemented in Matlab? I haven't checked that. Because in that case it makes more sense that it is implemented the way it is.  —[[User:Kri|Kri]] ([[User talk:Kri|talk]]) 09:05, 21 September 2014 (PDT)
12

edits