[Octave-bug-tracker] [bug #47502] geometry or mapping package: polysplit and polyjoin functions

[Juan Pablo Carbajal]

Follow-up Comment #1, bug #47502 (project octave):

Have we decided already whether these functions go to geometry or mapping?

In the meanwhile:

1. I prefer (x ~= 2) and not  ~(x == 2) 
2. Insert a blank space between "if" and conditions (Octave code style)
3. Introduce a blank space between any function and its arguments, e.g.
"isempty (x)" (Octave code style)
4. Keep consistent indentation.
5. If you use octave terminators like "endfunction" please also use "endif",
"endfor" etc...
6. Do not forget to always add your copyright notice to the header of your
file.
7. Use texinfo for the docuemntation
8. Write tests
9. Write at least one demo.
10. Try to use Octave's error ids (check error_ids)

Check the new version of the function I attach. There is room for improvement
in the documentation.






(file #36773)
    _______________________________________________________

Additional Item Attachment:

File name: polyjoin.m                     Size:2 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47502>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/