# Renaming API when facing non standard decisions

**URL:** <https://www.ruby-forum.com/t/renaming-api-when-facing-non-standard-decisions/134170>\
**Category:** Ruby-Gnome 2\
**Created:** [April 8, 2008, 4:05pm UTC](https://www.ruby-forum.com/t/renaming-api-when-facing-non-standard-decisions/134170 "2008-04-08T16:05:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blueprint](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/cc9497/32.png) [@blueprint](https://www.ruby-forum.com/u/blueprint)\
**Post date:** [April 8, 2008, 4:05pm UTC](https://www.ruby-forum.com/t/renaming-api-when-facing-non-standard-decisions/134170/1 "2008-04-08T16:05:12Z")

</div>

I have noticed that currently there are non standard decisions in  
Gdk:Display:

Gdk::Display#supports\_shapes  
Gdk::Display#supports\_input\_shapes

should be named:

Gdk::Display#supports\_shapes?  
Gdk::Display#supports\_input\_shapes?

because they return true or false. Is it ok to just rename them, or do  
we want to maintain compatibility with these incorrect names? There  
are not even documented on hiki, and probably seldom used, so I think  
we should maybe just rename them without compatibility…

–  
Guillaume C. - [http://zarb.org/~gc/](http://zarb.org/~gc/)

---

<div class="post-metadata">

**Author:** ![blueprint](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/cc9497/32.png) [@blueprint](https://www.ruby-forum.com/u/blueprint)\
**Post date:** [April 8, 2008, 4:11pm UTC](https://www.ruby-forum.com/t/renaming-api-when-facing-non-standard-decisions/134170/2 "2008-04-08T16:11:05Z")

</div>

Hi,

In [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
“[ruby-gnome2-devel-en] renaming API when facing non standard  
decisions” on Tue, 8 Apr 2008 16:04:53 +0200,  
“Guillaume C.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> because they return true or false. Is it ok to just rename them, or do  
> we want to maintain compatibility with these incorrect names? There  
> are not even documented on hiki, and probably seldom used, so I think  
> we should maybe just rename them without compatibility..

Ah, right. Please just rename.

## Thanks,

kou
