php-general Digest 4 Mar 2013 02:40:11 -0000 Issue 8147

Topics (messages 320370 through 320375):

Re: static Logging class?
        320370 by: shiplu
        320371 by: Ravi Gehlot
        320372 by: Larry Garfield
        320373 by: Lars Nielsen
        320375 by: Ravi Gehlot

Re: Holding "datetimes" in a DB.
        320374 by: Richard Quadling

Administrivia:

To subscribe to the digest, e-mail:
        php-general-digest-subscr...@lists.php.net

To unsubscribe from the digest, e-mail:
        php-general-digest-unsubscr...@lists.php.net

To post to the list, e-mail:
        php-gene...@lists.php.net


----------------------------------------------------------------------
--- Begin Message ---
You can use singleton pattern for this. Use one instance for whole
application.


-- 
Shiplu.Mokadd.im
ImgSign.com | A dynamic signature machine
Innovation distinguishes between follower and leader

--- End Message ---
--- Begin Message ---
Hello Lars,

I would apply the Singleton Pattern where you would have 1 instance for you
entire application. As far as whether or not to use a static method, I
would weigh the options. If you just want to call a method that you know
will not have to be changed in the future and that method will not be using
any pre-defined properties, then it makes sense to call a static method.
Bear in mind that static methods can not be overridden.

Best of luck,

-------------------------------------------------
  [image: logo]
*Ravi Gehlot
*
Mobile: 407-283-5282
Orlando, FL 32765-8085
http://www.RaviGehlot.Net/
https://github.com/ravigehlot

*"First, solve the problem. Then, write the code."*
[image: Twitter] <http://www.twitter.com/ravigehlot> [image:
LinkedIn]<http://www.linkedin.com/in/ravigehlot> [image:
Amazon]<https://www.amazon.com/gp/pdp/profile/A35NGY72YZSFR7?ie=UTF8&ref_=ya_56>
[image:
Meetup] <http://www.meetup.com/members/12029903/> [image:
pinterest]<http://pinterest.com/ravigehlot/> [image:
reddit] <http://www.reddit.com/user/ravigehlot/>
Contact me: [image: Google Talk] ravigehlot [image: Skype] ravigehlot [image:
Y! Messenger] ravigehlot


On Sun, Mar 3, 2013 at 8:26 AM, Lars Nielsen <l...@lfweb.dk> wrote:

> Hi,
>
> I work on a little hobby-project, and i want to make a oo logging
> facility. (php5.3 oop)
>
> Is it best to make a class with static functions that i can call from my
> other classes? Or is it more appropriate to make a real logging-class i
> should instantiate every time i need to log something? (I just want to
> log to a file)
>
> Best regards
> Lars Nielsen
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--- End Message ---
--- Begin Message --- Make a real classed object that you pass to various objects that need it. Otherwise you make your life way harder for unit testing. Don't have a class that self-enforces that it's a singleton. That way lies pain.

In particular, I recommend using or writing a class based on the PSR-3 recommendation:

https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md

There's even stock code for the interface and some useful base classes available:

https://packagist.org/packages/psr/log

And for added fun, there are already publicly available open source libraries that implement PSR-3 that you can just drop in and use, such as:

https://packagist.org/packages/monolog/monolog

(If that's too heavy for you, writing your own PSR-3 compatible logger is dead-simple.)


I'm sure you're about to say "zOMG this is just a hobby project, I don't need something that fancy and all injected and shit!" If it's a simple project, use a simple container to do all the hard work for you:

https://packagist.org/packages/pimple/pimple

(That's < 100 lines of executable code. Quite powerful, dead simple to use.)

Cheers.

--Larry Garfield, FIG member


On 03/03/2013 07:26 AM, Lars Nielsen wrote:
Hi,

I work on a little hobby-project, and i want to make a oo logging
facility. (php5.3 oop)

Is it best to make a class with static functions that i can call from my
other classes? Or is it more appropriate to make a real logging-class i
should instantiate every time i need to log something? (I just want to
log to a file)

Best regards
Lars Nielsen




--- End Message ---
--- Begin Message ---
Thanks a lot Larry! This PSR-3 looks just the way to do such things! :-)

I hope i chat with you at DrupalCon Praha!
http://www.linkedin.com/profile/view?id=18644639

Best regards
Lars Nielsen
> Make a real classed object that you pass to various objects that need
> it.  Otherwise you make your life way harder for unit testing.  Don't
> have a class that self-enforces that it's a singleton.  That way lies
> pain.
>
> In particular, I recommend using or writing a class based on the PSR-3
> recommendation:
>
> https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md
>
> There's even stock code for the interface and some useful base classes
> available:
>
> https://packagist.org/packages/psr/log
>
> And for added fun, there are already publicly available open source
> libraries that implement PSR-3 that you can just drop in and use, such as:
>
> https://packagist.org/packages/monolog/monolog
>
> (If that's too heavy for you, writing your own PSR-3 compatible logger
> is dead-simple.)
>
>
> I'm sure you're about to say "zOMG this is just a hobby project, I don't
> need something that fancy and all injected and shit!"  If it's a simple
> project, use a simple container to do all the hard work for you:
>
> https://packagist.org/packages/pimple/pimple
>
> (That's < 100 lines of executable code.  Quite powerful, dead simple to
> use.)
>
> Cheers.
>
> --Larry Garfield, FIG member
>
>
> On 03/03/2013 07:26 AM, Lars Nielsen wrote:
>> Hi,
>>
>> I work on a little hobby-project, and i want to make a oo logging
>> facility. (php5.3 oop)
>>
>> Is it best to make a class with static functions that i can call from my
>> other classes? Or is it more appropriate to make a real logging-class i
>> should instantiate every time i need to log something? (I just want to
>> log to a file)
>>
>> Best regards
>> Lars Nielsen
>>
>>
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--- End Message ---
--- Begin Message ---
Hello Larry,

Thanks for sharing!



-------------------------------------------------
  [image: logo]
*Ravi Gehlot
*
Mobile: 407-283-5282
Orlando, FL 32765-8085
http://www.RaviGehlot.Net/
https://github.com/ravigehlot

*"First, solve the problem. Then, write the code."*
[image: Twitter] <http://www.twitter.com/ravigehlot> [image:
LinkedIn]<http://www.linkedin.com/in/ravigehlot> [image:
Amazon]<https://www.amazon.com/gp/pdp/profile/A35NGY72YZSFR7?ie=UTF8&ref_=ya_56>
[image:
Meetup] <http://www.meetup.com/members/12029903/> [image:
pinterest]<http://pinterest.com/ravigehlot/> [image:
reddit] <http://www.reddit.com/user/ravigehlot/>
Contact me: [image: Google Talk] ravigehlot [image: Skype] ravigehlot [image:
Y! Messenger] ravigehlot


On Sun, Mar 3, 2013 at 1:48 PM, Larry Garfield <la...@garfieldtech.com>wrote:

> Make a real classed object that you pass to various objects that need it.
>  Otherwise you make your life way harder for unit testing.  Don't have a
> class that self-enforces that it's a singleton.  That way lies pain.
>
> In particular, I recommend using or writing a class based on the PSR-3
> recommendation:
>
> https://github.com/php-fig/**fig-standards/blob/master/**
> accepted/PSR-3-logger-**interface.md<https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md>
>
> There's even stock code for the interface and some useful base classes
> available:
>
> https://packagist.org/**packages/psr/log<https://packagist.org/packages/psr/log>
>
> And for added fun, there are already publicly available open source
> libraries that implement PSR-3 that you can just drop in and use, such as:
>
> https://packagist.org/**packages/monolog/monolog<https://packagist.org/packages/monolog/monolog>
>
> (If that's too heavy for you, writing your own PSR-3 compatible logger is
> dead-simple.)
>
>
> I'm sure you're about to say "zOMG this is just a hobby project, I don't
> need something that fancy and all injected and shit!"  If it's a simple
> project, use a simple container to do all the hard work for you:
>
> https://packagist.org/**packages/pimple/pimple<https://packagist.org/packages/pimple/pimple>
>
> (That's < 100 lines of executable code.  Quite powerful, dead simple to
> use.)
>
> Cheers.
>
> --Larry Garfield, FIG member
>
>
>
> On 03/03/2013 07:26 AM, Lars Nielsen wrote:
>
>> Hi,
>>
>> I work on a little hobby-project, and i want to make a oo logging
>> facility. (php5.3 oop)
>>
>> Is it best to make a class with static functions that i can call from my
>> other classes? Or is it more appropriate to make a real logging-class i
>> should instantiate every time i need to log something? (I just want to
>> log to a file)
>>
>> Best regards
>> Lars Nielsen
>>
>>
>>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--- End Message ---
--- Begin Message ---
On 1 March 2013 10:49, Richard Quadling <rquadl...@gmail.com> wrote:
> Hi.
>
> My heads trying to remember something I may or may not have known to start 
> with.
>
> If I hold datetimes in a DB in UTC and can represent a date to a user
> based upon a user preference Timezone (not an offset, but a real
> timezone : Europe/Berlin, etc.) am I missing anything?
>
> Richard.

Thank you to everyone who pitched in. My initial assumptions seem to hold.

Richard.

--- End Message ---

Reply via email to