#tyndur · 2010-01-29

51 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. taljethgn8
  2. quokgn8 taljeth :)
  3. kwolfMoin
  4. FreakyPenguinOha, da ist einer aus dem Bett gefallen
  5. pc[away]kwolf: ping
  6. kwolfpcmattman: pong
  7. pcmattmanJust going to touch up the documentation now and email you the udate
  8. pcmattman*update
  9. kwolfThe general documentation or mem.h?
  10. kwolfAnyway, I'm always happy with any updates ;-)
  11. pcmattmanmem.h
  12. kwolfOk. It's not only documentation but also the prototypes, right?
  13. pcmattmanNah, just documentation for now
  14. pcmattmanI haven't yet figured out the best name instead of cdi_mem_require_flags
  15. kwolfOh, no cdi_mem_quok_area yet? ;-)
  16. pcmattmanHehe
  17. pcmattmanNot yet ;)
  18. pcmattmankwolf: done, if the patch is malformed then I apologise in advance :)
  19. kwolfAre you out of practice, or why should it be?
  20. pcmattmanWell, see if it's malformed first ;)
  21. kwolfIn the archive it looks right
  22. kwolfHm, the diff to my original patch looks pretty empty?
  23. kwolfSure you sent the right patch?
  24. pcmattmanThere should be 5 lines difference
  25. kwolfRight, the header says so. Where are they? I can't seem to find them
  26. pcmattmanThey should be in the cdi_mem_require_flags documentation
  27. kwolfActually, vimdiff can't find them. It only shows corrupted UTF-8 characters ;-)
  28. pcmattmanIf they aren't there, they aren't all that important: just commit the patch
  29. pcmattmanThe added 5 lines just explained a possible usage scenario, is all
  30. kwolfI'd prefer to commit it only if we're happy with it
  31. kwolfAnd I think you're not happy with cdi_mem_require_flags
  32. pcmattmanIt'd be good to find an alternative name for it
  33. kwolfHm, check yourself, is your new paragraph there? http://list.tyndur.org/pipermail/cdi-devel/2010-January/000159.html
  34. pcmattmanIt isn't, must've messed it up somewhere
  35. pcmattmanI don't have original anymore either - I think it might be best to wait for a rename anyway.
  36. pcmattmanWith a decent rename extra documentation won't be required because the function name will make it more intuitive
  37. kwolfOk
  38. kwolfI'm just afaid that waiting won't solve the problem ;-)
  39. FreakyPenguin*g*
  40. pcmattmanI'd like to see if quok has any ideas
  41. pcmattmanOr FreakyPenguin ;)
  42. FreakyPenguinAt least no usable ideas ;-)
  43. kwolfI'm sure a Swiss word exists that hits the nail on the head but that noone else understands ;-)
  44. FreakyPenguinHm, don't know if we have any special words concerning driver interfaces. *g*
  45. kwolfI'm truly disappointed
  46. pcmattmanNight
  47. kwolfNight
  48. FreakyPenguingn8 pc[away]
  49. quokmoin
  50. XanClicMoin, quok
  51. kwolfMoin