4 ms·
This is, in essence, Hungarian notation. It's great. I wrote about it a few months ago: https://dev.to/jmpavlick/hungary-for-the-power-a-closer-look-at-hungar
by eckza 4y ago
This is, in essence, Hungarian notation. It's great.
I wrote about it a few months ago:
https://dev.to/jmpavlick/hungary-for-the-power-a-closer-look-at-hungarian-notation-282d https://dev.to/jmpavlick/hungary-for-the-power-a-closer-look...
- Supermancho 4y agoWhile there is evidence that hungarian notation + camelCase is better for token usage - eg variables Underscores are better for readability other kinds of things like unit test names or filenames. Because humans tend to shortcut, it becomes camelCase for everything, including other inappropriate attributes out of laziness, which is aggravating. It's too bad that distinction has not been properly subjected to rigor yet. http://www.cs.loyola.edu/~lawrie/papers/lawrieICPC09.pdf http://www.cs.loyola.edu/~lawrie/papers/lawrieICPC09.pdf
- eckza 4y agoHungarian notation is not "camelCase". It's a system for semantic variable naming.
- Supermancho 4y agoMade an edit to better serve your sensibilities SMH
- Kiro 4y agoYour post before your edit made no sense so don't give us that "SMH" BS.
- Kiro 4y agoYou can use Hungarian notation with underscores as well so not sure what you're getting at here. Sounds like you're talking about camelCase vs snake_case.
- DonHopkins 4y agoOr snake_that_swallowed_halfACamelCase. What Did Terrence Eat? https://www.youtube.com/watch?v=CAUxhXIeSc8 https://www.youtube.com/watch?v=CAUxhXIeSc8
- shikoba 4y ago> While there is evidence that hungarian notation + camelCase is better for token usage - eg variables What evidence? Where?
- DonHopkins 4y agoI submit to you, the Motif Angst Page. http://www.art.net/~hopkins/Don/unix-haters/x-windows/motif.html http://www.art.net/~hopkins/Don/unix-haters/x-windows/motif.... TLDR: s_CALLBACK_CUR_INSERT Lexical_Bindings_For_XmTextVerifyCallbackStruct XtPointer call_data XLTYPE_CALLBACKOBJ /* How long can this go on???? */ Set_Call_Data_For_XmTextVerifyCallbackStruct Wcb_Meta_Callbackproc XmAnyCallbackStruct doit newInsert XmCR_MODIFYING_TEXT_VALUE cdr car ep /* do nothing for most cases... */ Cvt_XmRXmString_to_LVAL GetValues_Union Resource_Instance WINTERP_MOTIF_111 XmStrings XtGetValues XtPointer_value cv_xmstring XmBulletinBoard XmNdialogTitle XmNnoMatchString XmNlabelString XmNtitleString XmRowColumn XtGetValues XmStringFree /* This is so totally ridiculous: there's NO WAY to tell Motif that any button can select a menu item. Only one button can have that honor. */ /* If this function looks like it does a lot more work than it needs to, you're right. Blame the Motif scrollbar for not being smart about updating its appearance. */ xm_update_scrollbar widget_instance Widget widget scrollbar_values pane_maximum widget_sliderSize new_sliderSize h_water l_water XtVaGetValues XmNheight XmNpaneMaximum XmNsliderSize widget_sliderSize XmNrefigureMode maximum minimum INT_MAX percent XmScrollBarSetValues ARMANDACTIVATE_KLUDGE DND_KLUDGE *dialog*button1.accelerators:#override Ctrl<KeyPress>m: ArmAndActivate() /* sets the parent window to 0 to fool Motif into not generating a grab */ USE_MOTIF xlw_unmunge_class_resize XlwMenuResize
- shikoba 4y agoWhat a proof...