Carbon has all of the functions inherited from the base Date Time class.
Credible carbon dating
Generally default values are the current date, time or timezone.
Higher values will wrap appropriately but invalid values will throw an defaults to the current timezone and otherwise can be a Date Time Zone instance or simply a string timezone value.
The only special case for default values (mimicking the underlying PHP library) occurs when an hour value is specified but no minutes or seconds, they will get defaulted to 0.
is done in the same timezone as the current instance.
There are several different methods available to create a new instance of Carbon. It overrides the parent constructor and you are best to read about the first parameter from the PHP manual and understand the date/time string formats it accepts.
You'll hopefully find yourself rarely using the constructor but rather relying on the explicit static methods for improved readability. All Date Time Zone parameters have been augmented so you can pass a Date Time Zone instance, string or integer offset to GMT and the timezone will be created for you.This is again shown in the next example which also introduces the $now = Carbon::now(); $now In London Tz = Carbon::now(new Date Time Zone('Europe/London')); // or just pass the timezone as a string $now In London Tz = Carbon::now('Europe/London'); // or to create a date with a timezone of +1 to GMT during DST then just pass an integer echo Carbon::now(1)-$now = Carbon::now(); echo $now; // 2016-06-24 $today = Carbon::today(); echo $today; // 2016-06-24 $tomorrow = Carbon::tomorrow('Europe/London'); echo $tomorrow; // 2016-06-25 $yesterday = Carbon::yesterday(); echo $yesterday; // 2016-06-23 functions allow you to provide as many or as few arguments as you want and will provide default values for all others.Note: I live in Ottawa, Ontario, Canada and if the timezone is not specified in the examples then the default of 'America/Toronto' is to be assumed.Typically Ottawa is -0500 but when daylight savings time is on we are -0400.Special care has been taken to ensure timezones are handled correctly, and where appropriate are based on the underlying Date Time implementation.For example all comparisons are done in UTC or in the timezone of the datetime being used.