Hill, Ronald wrote:
sub daytime_as_spanset {
my $self = shift;
my $class = ref($self);
my $sunrises = $self-sunrise_as_set;
my $sunsets = $self-sunset_as_set;
return $sunrises-until( $sunsets );
}
maybe sunrise_as_spanset? (land of the midnight sun)
Hill, Ronald wrote:
sub daytime_as_spanset {
my $self = shift;
my $class = ref($self);
my $sunrises = $self-sunrise_as_set;
my $sunsets = $self-sunset_as_set;
return $sunrises-until( $sunsets );
}
maybe sunrise_as_spanset? (land of the
Hill, Ronald wrote:
That would be great! I sure hope you can finish the API
so I can try it out!!
If you want to try it _before_ we have an API,
you can do it the undocumented way:
Let's say you already have a $sunrise_set and a $sunset_set,
since recurrence-sets are in the DateTime::Set API.
Speaking as an end user! I think that a module should either a) do
what the user expects or b) die because it's not possible to do
exactly what the user asked for. As I said I don't think turning
-0600 into UTC is reasonably what the user asked for.
Depends. Did they want output with
I think that depends on what the format is used for. With iCal, which is
focused on calendaring, it makes sense that it's okay to lose the specific
time zone, as long as the UTC time is correct.
Normalizing to UTC sounds a lot better then just tacking it on to fulfill the TZ
requirement.
