| 07:32.00 | *** join/#linuxpakistan Guest478 (~Guest478@202.133.44.134) |
| 07:32.39 | *** join/#linuxpakistan Guest262 (~Guest262@202.133.44.134) |
| 07:32.46 | *** part/#linuxpakistan Guest262 (~Guest262@202.133.44.134) |
| 10:31.59 | *** join/#linuxpakistan linuxg0d (linuxg0d@208.53.159.15) [NETSPLIT VICTIM] |
| 10:35.25 | *** join/#linuxpakistan linuxg0d (linuxg0d@208.53.159.15) [NETSPLIT VICTIM] |
| 10:39.32 | *** join/#linuxpakistan linuxg0d (linuxg0d@208.53.159.15) [NETSPLIT VICTIM] |
| 11:56.14 | *** join/#linuxpakistan Zehrila (KingCobra@202.123.241.216) |
| 13:56.15 | *** join/#linuxpakistan mathrick (~mathrick@195.116.35.55) |
| 14:45.22 | *** join/#linuxpakistan fawad (~fawad@8c81af3164ad1945.session.tor) |
| 17:54.13 | *** join/#linuxpakistan u_int32_t (~im_an_int@ghruaim.net) |
| 18:32.37 | fawad | hey u_int32_t! |
| 18:32.57 | fawad | any idea about how xsd restrictions work? |
| 18:33.41 | u_int32_t | fawad, nope |
| 18:33.44 | u_int32_t | didnt know that existed |
| 18:34.13 | fawad | damn. |
| 18:34.26 | fawad | i want to allow either 2-4 characters in an attribute, or empty. |
| 18:34.35 | fawad | that 'or empty' part is baffling me. |
| 18:35.24 | *** join/#linuxpakistan L|NUX (~linux@202.5.145.54) |
| 18:44.04 | u_int32_t | fawad, that sounds like a regex to me |
| 18:55.57 | fawad | u_int32_t: nah. found a cleaner solution. |
| 18:56.40 | fawad | i take the type i created for the '2-4 characters' enforcement, union that with a type that only allows an empty string, and use the resultant type for the element. |
| 18:56.44 | fawad | clever, eh? |
| 21:32.40 | linuxg0d | hmm |
| 21:43.53 | *** join/#linuxpakistan anjumbutt (~anjumbutt@203.135.26.5) |
| 21:52.27 | fawad | praise the lord! sarge is out! |
| 22:10.19 | linuxg0d | y he quiet |
| 22:11.16 | linuxg0d | i think try to use tor |
| 22:15.17 | *** join/#linuxpakistan u_int32_t (debian-tor@b149465c97fd95fd.session.tor) |
| 22:41.01 | u_int32_t | fawyou're gay |
| 22:41.08 | u_int32_t | doh |