Re: [OctDev] Release details

[Paul K. <pki...@us...>]

On Sep 9, 2004, at 3:54 AM, David Bateman wrote:

> According to Josep Mon=E9s i Teixidor <jm...@pu...> (on=20
> 09/09/04):
>> cmpermute and uintlut don't work in 2.1.57 (with all the uint=BF =
stuff=20
>> it
>> hasn't got much sense) but qtdecomp does.
>
> Then it probably makes sense to move cpermute.m and uintlut.m to
> cpermute.m.in and uintlut.m.in respectively, then add something
> like the following to your makefile
>
> t2.1.58=3Dcpermute.m uintlut.m
> UINT_TARGETS=3D$($(word 1, $(sort t$(OCTAVE_VERSION) t2.1.58)))
>
> all : $(UINT_TARGETS) onv2.oct cordflt2.oct bwlabel.oct bwfill.oct \
> 	rotate_scale.oct houghtf.oct graycomatrix.oct \
> 	$(JPEG) $(PNG)
>
> %.m: %.m.in
>         -$(INSTALL) $< $@
>
> In that way the m-files don't exist for vesrions of octave prior to=20
> 2.1.58

I'm not so keen on this.  I don't mind shipping a function that doesn't=20=

work
on older versions of octave, so long as it doesn't crash.  In this case=20=

the
functions exit with errors saying things like uint8 doesn't exist.

This is different from functions which are removed to avoid conflict=20
with
new octave functions.

- Paul