Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.php

comp.lang.php

18446 articles (numbers 823 – 19616) — threaded view

| Advanced

Subject Author Date [asc]
Re: javascript to php in the same page Lew Pitcher <lew.pitcher@digitalfreehold.ca> 2016-02-14 11:08 -0500
Re: javascript to php in the same page Ben Bacarisse <ben.usenet@bsb.me.uk> 2016-02-14 16:43 +0000
Re: javascript to php in the same page Luuk <luuk@invalid.lan> 2016-02-14 17:50 +0100
Re: javascript to php in the same page "Christoph M. Becker" <cmbecker69@arcor.de> 2016-02-14 18:17 +0100
Re: javascript to php in the same page Luuk <luuk@invalid.lan> 2016-02-14 19:42 +0100
Re: javascript to php in the same page Tim Streater <timstreater@greenbee.net> 2016-02-14 19:21 +0000
Re: javascript to php in the same page Ben Bacarisse <ben.usenet@bsb.me.uk> 2016-02-14 21:40 +0000
Re: javascript to php in the same page Arno Welzel <usenet@arnowelzel.de> 2016-02-15 13:51 +0100
casting to integer bill <william@TechServSys.com> 2016-02-15 08:14 -0500
Re: casting to integer: solved bill <william@TechServSys.com> 2016-02-15 08:16 -0500
Re: javascript to php in the same page Erwin Moller <erwinmollerusenet@xs4all.nl> 2016-02-15 14:49 +0100
Re: casting to integer Arno Welzel <usenet@arnowelzel.de> 2016-02-15 18:08 +0100
Re: javascript to php in the same page Ben Bacarisse <ben.usenet@bsb.me.uk> 2016-02-15 19:20 +0000
OT: wasted bytes Richard Yates <richard@yatesguitar.com> 2016-02-15 21:39 -0800
Re: OT: wasted bytes "Christoph M. Becker" <cmbecker69@arcor.de> 2016-02-16 12:21 +0100
Re: casting to integer bill <william@TechServSys.com> 2016-02-16 06:47 -0500
Considering a new programming language after years with Visual Basic wrong.address.1@gmail.com 2016-02-16 05:45 -0800
Re: OT: wasted bytes Jerry Stuckle <jstucklex@attglobal.net> 2016-02-16 09:19 -0500
Re: Considering a new programming language after years with Visual Basic Jerry Stuckle <jstucklex@attglobal.net> 2016-02-16 09:36 -0500
Re: Considering a new programming language after years with Visual Basic Gary Peek <peek@industrologic.com> 2016-02-16 11:21 -0600
Re: Considering a new programming language after years with Visual Basic James Wang <jwang25610@gmail.com> 2016-02-17 01:09 -0800
PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> 2016-02-17 09:37 +0000
Functions behaving badly: PHP str_split on an empty string James Harris <james.harris.1@gmail.com> 2016-02-17 09:57 +0000
Re: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> 2016-02-17 11:05 +0100
Re: Considering a new programming language after years with Visual Basic James Harris <james.harris.1@gmail.com> 2016-02-17 10:07 +0000
Re: Functions behaving badly: PHP str_split on an empty string "Christoph M. Becker" <cmbecker69@arcor.de> 2016-02-17 11:53 +0100
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 08:19 -0500
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 14:43 +0100
Re: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> 2016-02-17 15:04 +0100
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 15:17 +0100
Re: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> 2016-02-17 15:47 +0100
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 09:55 -0500
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 09:56 -0500
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 15:57 +0100
Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> 2016-02-17 15:04 +0000
Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> 2016-02-17 15:15 +0000
Re: PHP processing steps to apply to a URL to make it safe "Christoph M. Becker" <cmbecker69@arcor.de> 2016-02-17 16:38 +0100
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 16:39 +0100
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 16:44 +0100
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 10:54 -0500
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 10:56 -0500
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 10:57 -0500
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 11:00 -0500
Re: Functions behaving badly: PHP str_split on an empty string James Harris <james.harris.1@gmail.com> 2016-02-17 16:04 +0000
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 11:05 -0500
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 17:10 +0100
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 12:11 -0500
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 12:12 -0500
Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> 2016-02-17 18:51 +0100
Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> 2016-02-17 12:55 -0500

« Previous 1 ... 62 63 64 65 66 ... 369 Next »


csiph-web