[Request] Allow "longitude" and "latitude" argument names

Neozaru · 2012-09-28T22:13:57.000Z

Hello.

I am developing a C++ Twitter API library. (https://github.com/Neozaru/LibTwitter-Core)
I use C++ var names , and send them directly in HTTP requests.

-> Problem : The argument “long” (for “longitude”) is also a keyword, in C++ (ie: long int), and most compilers will reject it.

Is it possible to allow “longitude” and “latitude” args for defining “lat” and “long” (“lon” could also be a solution).
Of course, I don’t request name replacement, but more flexibility with these parameters.

Thanks.

episod · 2012-10-01T14:28:06.000Z

Does your C++ interpreter have trouble telling the difference between a string called “long” and the actual functional keyword?

Neozaru · 2012-10-01T16:24:18.000Z

Compiler*
Yes, that’s the problem

kurrik · 2012-10-01T17:43:10.000Z

Just, to verify, you would like us to change the API because your code generator is not capable of differentiating between parameter names you send in a HTTP request, vs the names of variables defined in this file:

github.com

Neozaru/LibTwitter-Core/blob/master/generator/twitter_methods.txt

:: mentions_timeline:: int count 20, usr_id_t since_id DEF, int max_id DEF, bool trim_user false, bool contributor_details false, bool include_entities true :: GET :: statuses/mentions_timeline
/* Doc here for "mentions_timeline"  */
:: user_timeline_by_id :: usr_id_t user_id, int count DEF, twt_id_t since_id DEF, twt_id_t max_id DEF, bool trim_user false, bool exclude_replies false, bool contributor_details false, bool include_rts true :: GET :: statuses/user_timeline
:: user_timeline :: usr_name_t screen_name, int count DEF, twt_id_t since_id DEF, twt_id_t max_id DEF, bool trim_user false, bool exclude_replies false, bool contributor_details false, bool include_rts true :: GET :: statuses/user_timeline
:: home_timeline :: int count DEF, usr_id_t since_id DEF, int max_id DEF, bool trim_user false, bool exclude_replies false, bool contributor_details false, bool include_entities true :: GET :: statuses/home_timeline

# STATUSES
:: get_retweets :: twt_id_t id, int count 50, bool trim_user false :: GET :: statuses/retweets/:id
:: show_status :: twt_id_t id, bool include_my_retweet true, bool trim_user false, bool include_entities true :: GET :: statuses/show/:id
:: destroy_status :: twt_id_t id, bool trim_user false :: POST :: statuses/destroy/:id
:: update_status :: string status, string in_reply_to_status_id DEF, string place_id DEF, bool display_coordinates false, bool trim_user false, float lat DEF, float lon DEF :: POST :: statuses/update
:: retweet :: twt_id_t id, bool trim_user false :: POST :: statuses/retweet/:id

# DONE MANUALLY : update_status_media

:: oembed_status :: twt_id_t id, string url, int maxwidth DEF, bool hide_media false, bool hide_thread false, bool omit_script false, string align "center", string related DEF, lang_t lang DEF :: GET :: statuses/oembed
:: search_tweets :: string q, string locale DEF, string result_type DEF, int count DEF, string until DEF, twt_id_t since_id DEF, twt_id_t max_id DEF, bool include_entities true, string callback DEF :: GET :: search/tweets

# DIRECT MESSAGES
#:: direct_messages :: int count DEF, int page DEF, usr_id_t since_id DEF, string max_id DEF, bool include_entities true, bool skip_status false :: GET :: direct_messages

This file has been truncated. show original

?

Neozaru · 2012-10-01T18:22:00.000Z

Actually, the problem is more complicated.

In my .cpp code, I have functions like :

do_something_request( string screen_name, int count, … );

I defined macros in order to get directly var names (screen_name, count) as “string” to define value. For the var <screen_name>, the key/value member will be “screen_name”=<value_of_var>.

–> In other words : Var names in my code are parameter keys in requests

This method allow me to save many lines of code, and the only problem comes when I set “long” as var name (because “long” is also a type/keyword, in C++)

See : https://github.com/Neozaru/LibTwitter-Core/blob/master/src/Twitter/Core/RequestCreator.h

Of course, I could correct this manually (I could use “LONG”, and in my Macros, I could check for “LONG”, and convert it to “long”), but if other coders wants to fork the project and add their custom requests (If API is updated, etc), they could meet some problems.

To avoid any ambiguity, i’m not requesting modification right now, but I submit the idea to be flexible on the name of these arguments for future patches/updates.

Thank you for your response. Sorry for my bad English.