Numerical applications will get a significant boost if
N-dim arrays with native slicing are possible in perl6.
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
time a new leap second is added :-)
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
lue
of time() and retrieve that from the equivalent date() object I will be
happy.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
ion.
In fact RFC #7 ("Higher Resolution time values") suggests that the
concept of "number of seconds since epoch" will have to make room for
fractions of a second anyway.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
4 bit mantissa).
> double has many more. But even I don't think using years as the
> "unit" is right thing to do.
>
> Seconds is my favourite...
>
Just to clarify, MJD is days not years. A 32-bit double preicision number
is usually adequate -- although have not thought about nano seconds!
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
the disadvantages:
>
>1. Unix time() no longer the basis for date
>
> Although that really isn't a disadvantage, just a difference.
Indeed.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
eneric and remove dependency on unix epoch with little
extra code.
Feel free to tell me to use an external module though. I had to mention it
though.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
he SLALIB
astrometry library (used by telescopes around the world). It tells you
the difference between UT, UTC, GMT and others.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
On Mon, 7 Aug 2000, Philip Newton wrote:
> On Mon, 7 Aug 2000, Tim Jenness wrote:
>
> > Is localtime() used often enough to justify being part of
> > the language?
>
> You're kidding, right?
>
> We wouldn't have had all those script kiddies complaining
ut of hand (although in principal Julian
date could be the internal format :-) ). What is the reason why any of
this has to be in the core? Could all the date/time stuff be moved into a
standard module? Is localtime() used often enough to justify being part of
the language?
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
ow the stringification to know about different
languages?
Also, I would vote for a method to return the Julian date (yes I am an
astronomer...) :-)
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
ge
if they are tweaked in pakcage "Foo". This would then keep Dan happy with
the perlish global approach but would prevent module authors from messing
with each others globals without realising it.
Of course, from what I can see, most of the globals don't really need to
be global
d to its name.
When I first started perl (coming from Fortran) I also had trouble sifting
through the docs working out how to remove a file but once I knew it was
unlink I simply used it because that was the perl command for "rm".
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
ditionally, generically it would not necessarily have to be a range of
integers. The range could be specified as floating point if we are
specifying a slice in physical coordinates.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
dl already allows(but that's an intereactive shell so we
try to reduce common typing as much as possible).
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
d comment on it rather than
writing an RFC that might duplicate things in less than 24 hours.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
verhead. All of the current open functions simply pass these
objects around.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
On Fri, 4 Aug 2000, Simon Cozens wrote:
> On Thu, Aug 03, 2000 at 09:39:30AM -1000, Tim Jenness wrote:
> > Reading through the docs for perl prototypes I see that there is a
> > reference to "named parameters" being a possibility in future versions of
> > perl.
&
te on the issue
some time ago).
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
smacks of FileHandle. That
> wasn't the intent. I propose a new name, "fileobject", that can refer to
> something that handles any of these:
sysopen() should probably be included in the list as well.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
that bothers me. Even the core modules
> can't agree, but that is a discussion for the stdlib list.
>
Isn't there some way to make $! usable when returning from normal subs as
well as from syscalls? It seems that $! goes a long way to providing the
an error message/error numb
eful, at minimum, to allow date arithmetic on these objects.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
't locate object method "autoflush" via package "IO::Handle" at ./test.pl line 5.
It seems that this issue is definitely worth a quick RFC - something
like "proposal to return filehandles from open/opendir rather than supply
as arguments". Whether this should be
File does it
$fh = new IO::File("< $filename");
and it returns undef on failure.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
ame it so as
not to clash with the underlying C function. No one has yet proposed an
RFC that removes all the standard C-like functions and replaces them with
objects (although given the brain storming going on at the moment I am
actually quite surprised noone has done that yet :-)
--
Tim Jenness
very fast and
perlified. I use it for my numeric programming.
I like Dan's suggestions though. The above array processing
would be very useful for string arrays as PDL can only deal with numbers.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
Windows users feel less confused.
It gets my vote so long as perl6 has really fast methods.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
is sometimes desirable, it seems like a overload.
>
Not if it is done as
=begin multiline comment
Multiline commend goes
here
=end multiline comment
=cut
but that is a bit more verbose...
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
een integers, floats and doubles though. Scalars, hashes
arrays and blessed objects provide more than enough breadth for me.
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
ence"
(allowing you to pass in a scalar containing a hash ref as well as a
hash). Would that cover what you want?
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
Yes.
> (Consistent with what? With itself.)
> And the manual will reflect _everything_. If it's not documented, it
> might as well not exist.
Agreed. The localtime() docs suffer from a 'read the C manual' problem at
the moment
--
Tim Jenness
JCMT software engineer/Support scientist
http://www.jach.hawaii.edu/~timj
at 0? I have to agree with Chaim and disagree
> vehemently that localtime() should be changed.
>
> -Nate
>
In my opinion the important change is pre-adding the 1900 to the year. I
find this always has to happen any way so it may as well be automatic.
The month and day indices should sta
32 matches
Mail list logo
