octave-dev

[OctDev] date/time functions

[William P. Y. H. <wil...@gm...>]

My new version of ver.m needs datestr and datenum, which are in
octave-forge. Are they ready for inclusion into Octave?

Paul, since most of the functions in main/time have your copyright on
them, would you like to tidy them up for inclusion into Octave? ;)

--
William Poetra Yoga Hadisoeseno

Re: [OctDev] date/time functions

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

You are welcome to submit anything in octave-forge for inclusion in=20
Octave.

Can you do what you need in ver.m using the native octave functions=20
strftime and strptime?

Ultimately datestr and datenum should be part of octave since they=20
extend date handling beyond the 1970-2038 supported by unix functions.

- Paul

On Dec 10, 2005, at 12:14 AM, William Poetra Yoga Hadisoeseno wrote:

> My new version of ver.m needs datestr and datenum, which are in
> octave-forge. Are they ready for inclusion into Octave?
>
> Paul, since most of the functions in main/time have your copyright on
> them, would you like to tidy them up for inclusion into Octave? ;)
>
> --
> William Poetra Yoga Hadisoeseno
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log=20=

> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD =
SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>

Re: [OctDev] date/time functions

[William P. Y. H. <wil...@gm...>]

Ignoring the regexp issue for the moment, I've tidied up the functions
+ calendar: ready for inclusion into octave
+ datenum: ready for inclusion into octave
+ datestr: ready for inclusion into octave, but it uses strfind, which
is not in octave yet
+ datevec: ready for inclusion into octave, but it relies on
__date_str2vec__, which is not ready yet
+ eomday: ready for inclusion into octave
+ now: ready for inclusion into octave
+ weekday: ready for inclusion into octave

Please check the functions (included in the attachment) and comment on
them. In particular, I think __date_str2vec__ (was datesplit) needs to
be re-rewritten. Can someone please help me with this?

I think strfind is also easy. Can someone tidy up strfind in
octave-forge and import it into octave?

--
William Poetra Yoga Hadisoeseno

Re: [OctDev] date/time functions

[William P. Y. H. <wil...@gm...>]

Sorry, I forgot to attach the files.

Re: [OctDev] date/time functions

[William P. Y. H. <wil...@gm...>]

On 12/20/05, William Poetra Yoga Hadisoeseno <wil...@gm...> wrot=
e:
> OK, I thought it would be more useful, but later I decided unnamed
> tokens are good enough. I'm thinking of using strptime, though, to
> reduce the size of __date_str2vec__ and increase the likelihood of it
> being accepted ;) Any ideas? Suggestions?
>

I've submitted a patch for strptime (I sent it to bu...@oc...).
I've also merged __date_str2vec__.m into datevec.m (attached). Please
comment on it.

--
William Poetra Yoga Hadisoeseno