Hello!
x="abc"
x&.nolength raises an error?!
is there any difference to .try ?
Where is it documented?
ri doesnt find it
mri Ruby v2.3.0
Is it worth to switch to the newest version? (any new features? found only
bugfixes since v230
Thanks Berg
"_only_ bugfixes" ??
Why would you *not* upgrade to a less buggy version of anything? 
···
On Wed, Aug 10, 2016 at 5:38 AM, A Berger <aberger7890@gmail.com> wrote:
Is it worth to switch to the newest version? (any new features? found only
bugfixes since v230
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote
Have a look at The Safe Navigation Operator (&.) in Ruby - Georgi Mitrev
&. checks that the receiver is not nil before trying the method call
Hope this helps,
Mike
···
On Aug 10, 2016, at 8:38 AM, A Berger <aberger7890@gmail.com> wrote:
Hello!
x="abc"
x&.nolength raises an error?!is there any difference to .try ?
Where is it documented?
ri doesnt find it
mri Ruby v2.3.0Is it worth to switch to the newest version? (any new features? found only bugfixes since v230
Thanks Berg
--
Mike Stok <mike@stok.ca>
http://www.stok.ca/~mike/
The "`Stok' disclaimers" apply.
Ok, so no method_missing !
Thank you!
···
Am 10.08.2016 14:54 schrieb "Mike Stok" <mike@stok.ca>:
On Aug 10, 2016, at 8:38 AM, A Berger <aberger7890@gmail.com> wrote:
Hello!
x="abc"
x&.nolength raises an error?!is there any difference to .try ?
Where is it documented?
ri doesnt find it
mri Ruby v2.3.0Is it worth to switch to the newest version? (any new features? found only
bugfixes since v230Thanks Berg
Have a look at The Safe Navigation Operator (&.) in Ruby - Georgi Mitrev
&. checks that the receiver is not nil before trying the method call
Hope this helps,
Mike
--
Mike Stok <mike@stok.ca>
Mike StokThe "`Stok' disclaimers" apply.
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
patch-level releases like 2.3.1, 2.3.2, 2.3.3, ...
(the latter are not yet released) do not introduce
new features; they usually fix bugs or security issues.
But note that depending on what you are doing,
bug/security fixes can be very critical (like e.g.
for the production environment of a web app).
Regards,
Marcus
···
Am 10.08.2016 um 14:38 schrieb A Berger:
Is it worth to switch to the newest version? (any new features? found
only bugfixes since v230
--
GitHub: stomar (Marcus Stollsteimer) · GitHub
PGP: 0x6B3A101A
Hi
sounds mystic, but updating from source is very much work...
Berg
···
Am 10.08.2016 15:51 schrieb "Hassan Schroeder" <hassan.schroeder@gmail.com>:
On Wed, Aug 10, 2016 at 5:38 AM, A Berger <aberger7890@gmail.com> wrote:
> Is it worth to switch to the newest version? (any new features? found
only
> bugfixes since v230"_only_ bugfixes" ??
Why would you *not* upgrade to a less buggy version of anything?
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
Hassan Schroeder | about.me
twitter: @hassan
Consulting Availability : Silicon Valley or remoteUnsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
The solution: use an installer or a version manager,
see https://www.ruby-lang.org/en/documentation/installation/\.
But unless you are using the installation in production,
always updating to the latest version is probably not
necessary.
Regards,
Marcus
···
Am 10.08.2016 um 17:30 schrieb A Berger:
Hi
sounds mystic, but updating from source is very much work...
Berg
--
GitHub: stomar (Marcus Stollsteimer) · GitHub
PGP: 0x6B3A101A