« first day (76 days earlier)      last day (3127 days later) » 

Suever
Suever
02:53
@LuisMendo I went ahead and made the MATL-Online repo not private any more since we're close to having it fully functional.
github.com/suever/MATL-Online
 
13 hours later…
Luis Mendo
Luis Mendo
15:38
@Suever Great! Pinned :-)
I keep seeing those "build passing" etc banners in GitHub. What do they mean? Is there some convention as to which or when should they be included?
@Suever The link to https://github.com/lmendo/MATL in the README file is missing the h
BTW I intended to include mat2str in MATL. I realized it doesn't support cell arrays, so I wrote a generalization here
Suever
Suever
15:54
@LuisMendo Well so there is a whole suite of tests that I have written for the app that get run automatically every time I commit anything to ensure that I don't completely break the functionality.
For MATL you don't have any automatic tests (I could help you write some if you wanted) so the services that provide those badges don't really apply to MATL
While octave doesn't have the builtin unit testing framework that MATLAB has, there are some alternative libraries out there that provide roughly the same functionality
But if you click on those badges they link to the sites that generate them and they give more information about what the badge means etc.
Luis Mendo
Luis Mendo
16:26
@Suever Thanks for the clarification! It sounds interesting, but too complicated for me, at least for now :-)
I've just created my first GitHub pull request :-) I hope I've done it correctly
It's just the link thing I mentioned above
Suever
Suever
Well done! I'll merge it in shortly here.
It's not too hard to write at least a basic set of tests. Basically just expected output for known input. It's pretty handy when you fix some bugs just to make sure that a given fix didn't introduce new ones and to ensure that the bugs stay fixed when future changes are made.

« first day (76 days earlier)      last day (3127 days later) »