2015-04-29 14:07 GMT+02:00 Tim Brown <[email protected]>:

> On 29/04/15 11:44, Stephen De Gabrielle wrote:
>
>> Are there any tasks suitable for Rosetta Code that are difficult or
>> impossible in other languages like Python or TCL? (or Lisp,
>> JavaScript, Self/Smalltalk, Forth ...)
>>
>
> Something specifically tuned to macros?
>
> Actually, (on a cursory search) there are no "Anaphoric" tasks; and
> Lisp is always so full of itself with "aif" et al.
>
> I think, though that this goes against the spirit of Rosetta Code's
> mission:
>
> From the very top of http://rosettacode.org/wiki/Rosetta_Code:
>
>> ... The idea is to present solutions to the same task in as many
>> different languages as possible, to demonstrate how languages are
>> similar and different, and to aid a person with a grounding in one
>> approach to a problem in learning another.
>>
>
>
Well, they include gems like:

    http://rosettacode.org/wiki/Break_OO_privacy

Quoting:

Show how to access private or protected members of a class in an
object-oriented language from outside an instance of the class, without
calling non-private or non-protected members of the class as a proxy. The
intent is to show how a debugger, serializer, or other meta-programming
tool might access information that is barred by normal access methods to
the object but can nevertheless be accessed from within the language by
some provided escape hatch or reflection mechanism. The intent is
specifically not to demonstrate heroic measures such as peeking and poking
raw memory.

Note that cheating on your type system is almost universally regarded as
unidiomatic at best, and poor programming practice at worst. Nonetheless,
if your language intentionally maintains a double-standard for OO privacy,
here's where you can show it off.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to