Re^2: Benefits of everything is an object? Or new sigils?

As far as I understand these packages simplify the workaround I sketched...

> If you keep both %employees and $employees in the same scope it would provide a (really ugly) way of keeping the original array|hash and its blessed reference

yeah indeed ugly, thats what I meant.

> I don't this is some 'problem' which requires the use of slow modules like autobox ...

Contrary to the believe of the group that flames against me, I'm not propagating autobox as an existing solution! (I was asking a question in another thread about autobox and hit the nerve of a group of united fanboys. But I'm tired to repeat this!)

I was talking about the theoretical benefits JS has over Perl in this respect, because there a hash acn be treated as object right from the beginning.

Tieing this hash provides the same functionality in Perl like altering the object in JS (Phase 2)

BTW: According to the docs, autobox isn't slower than method calls on blessed references. >or some wholesale re-invention of Perl symbology.

A Sigil for each Ref-Type would open a lot of simplifications for problems newbies face when starting to learn Perl.

Believe it or not, many people stop and hate Perl just because of these problems...long before even entering a level allowing to understand Data::AsObject and Hash::AutoHash.

Many thanx for your contribution, it's one of the better ones lifting the level of this discussion! :)

Cheers Rolf

Comment on Re^2: Benefits of everything is an object? Or new sigils?

Replies are listed 'Best First'.
Re^3: Benefits of everything is an object? Or new sigils? by james2vegas (Chaplain) on Mar 04, 2010 at 21:18 UTC
In a way you could say there is a sigil for each ref-type, when it gets deferenced (or when it is actually used as the base type, and not a reference in a scalar), `@ => @$`, `% => %$`, `& => &$`. For amusement or other purpose, here is code that lets you use a hashref or hash (or arrayref or array) by blessing the former (and the ref of the latter) into an (initially) non-existent package, and then create a function in that package. The function can be called in the usual way ($blessedref->function), but can also be called with NameSpace::function(%indirectlyblessedhash) owing to the \% prototype on the function which uses the reference of that parameter. If you use references for your data structures instead of plain hashes and arrays, and bless those references into appropriate packages (and dereference where needed), you will have the equivalent functionality to javascript array\|objects. For me, at least, the requirement (softened by autobox), that objects be scalars makes sense, as scalars are for holding one value (base type or object) at a time. Read more... (597 Bytes)	[reply] [d/l] [select]
Re^4: Benefits of everything is an object? Or new sigils? by LanX (Saint) on Mar 04, 2010 at 23:54 UTC
> In a way you could say there is a sigil for each ref-type, when it gets deferenced (or when it is actually used as the base type, and not a reference in a scalar), @ => @$, % => %$, & => &$. Alas, it's more complicated than this. Just to give you one example, if you have a nested structure you have to write something like `push @{ $ref->[1][2][3] }, "elem"` Very motivating for beginners! :( In most other languages you can simply write something like `push ref[1][2][3] , "elem"` ... Cheers Rolf	[reply] [d/l] [select]