You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by "Philip M. Gollucci" <ph...@p6m7g8.com> on 2003/03/04 16:58:38 UTC
Source Code Oraginzation
I need good reasons why to do the following
/cgi-bin
*.pm
*.plex files (PerlEX)
*.cgi files
_no subdirectories_
VS
/cgi-bin
*.plex
*.cgi
packages/AMS/
some *.pm files
more directories with other *.pm files
OOP approach
Not quite sure where this one goes, but I know everyone here are more then
qualified to answer this.
I recently took shit for doing this, and I know at the _very_ least this
is correctly from a security standpoint as now _ALL_ our code is out of
web space. I need other good reasons as well, other then for organization.
Also, documenting where a function is located ?
I like the namespace prefix
package HomeScreens;
....
@EXPORT = (
hs_*
)
sub hs_* {
}
sub not_exported_func { }
VS
Export nothing
and use &HomeScreens::hs_*();
I'd like to hear agruments for and against.
END
------------------------------------------------------------------------------
Philip M. Gollucci philip@p6m7g8.com 301.474.9294 301.646.3011 (cell)
Science, Discovery, & the Universe (UMCP)
Webmaster & Webship Teacher
URL: http://www.sdu.umd.edu
eJournalPress
Database/PERL Programmer & System Admin
URL : http://www.ejournalpress.com
Resume : http://p6m7g8.net/Resume
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [users@httpd] Source Code Oraginzation
Posted by "Philip M. Gollucci" <ph...@p6m7g8.com>.
On Tuesday 04 March 2003 22:39, Jacob Coby wrote:
> I like automatic documentation generators.
I agree, I'd use DockBook, but its not that great for PERL at least according
to it. Any suggestions ?
I have small homegrown one listing what globals variables, config variables
Arguments, and return lines a function uses/sets.
--
END
------------------------------------------------------------------------------
Philip M. Gollucci philip@p6m7g8.com 301.474.9294 301.646.3011 (cell)
Science, Discovery, & the Universe (UMCP)
Webmaster & Webship Teacher
URL: http://www.sdu.umd.edu
eJournalPress
Database/PERL Programmer & System Admin
URL : http://www.ejournalpress.com
Resume : http://p6m7g8.net/Resume
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Source Code Oraginzation
Posted by Jacob Coby <jc...@listingbook.com>.
>>I kept telling him that; but Mr. 10 years of expience at AOL, Bell Labs,
and
AT&T as a Sybase DBA "knows better"<<
He's a DBA?!? Let him design schemas, views, and stored procs. ;-)
>>After giving the other reasons, still wanted more citing he can't find
things.
I say grep -r or grep -R for a great majority of systems works great
including every single one we use.<<
grep -rn is great. Use it all the time.
We actually split up usage from implementation via libraries and directories
(PHP). It actually makes some things easier -- for example finding the
usage of a function vs finding the implementation.
It makes it easier to keep track of what does what. You know that
everything in cgi-bin/ reacts to something in one way or another. And you
know that everything in lib/ does something, and may or may not render
anything. But you know that everything in lib/ cannot be exploited since
there is no code entry point -- just a bunch of functions and defines and
whatnot.
You also don't have a big clusterfuck of files to wade through. That means
more than it might seem after a while.
-Jacob
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Source Code Oraginzation
Posted by "Philip M. Gollucci" <ph...@p6m7g8.com>.
I kept telling him that; but Mr. 10 years of expience at AOL, Bell Labs, and
AT&T as a Sybase DBA "knows better"
After giving the other reasons, still wanted more citing he can't find things.
I say grep -r or grep -R for a great majority of systems works great
including every single one we use.
On Tuesday 04 March 2003 22:39, Jacob Coby wrote:
> >>I recently took shit for doing this, and I know at the _very_ least this
>
> is correctly from a security standpoint as now _ALL_ our code is out of
> web space. I need other good reasons as well, other then for
> organization.<<
>
> It's more secure, and more organized. The two panceas of programming.
> What else do you need? I hear that putting code outside the DocRoot makes
> you irresistable to the opposite sex. It also cures athletes foot and
> stops sniffles.
>
> >>Also, documenting where a function is located ?<<
>
> I like automatic documentation generators.
>
> >>I'd like to hear agruments for and against.<<
>
> Namespaces are great, as long as you do a bit of planning beforehand. You
> don't really want to figure out which of 32 namespaces that function
> DoSomethingReallyUseful() is in.
>
> -Jacob
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
--
END
------------------------------------------------------------------------------
Philip M. Gollucci philip@p6m7g8.com 301.474.9294 301.646.3011 (cell)
Science, Discovery, & the Universe (UMCP)
Webmaster & Webship Teacher
URL: http://www.sdu.umd.edu
eJournalPress
Database/PERL Programmer & System Admin
URL : http://www.ejournalpress.com
Resume : http://p6m7g8.net/Resume
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Source Code Oraginzation
Posted by Jacob Coby <jc...@listingbook.com>.
>>I recently took shit for doing this, and I know at the _very_ least this
is correctly from a security standpoint as now _ALL_ our code is out of
web space. I need other good reasons as well, other then for
organization.<<
It's more secure, and more organized. The two panceas of programming. What
else do you need? I hear that putting code outside the DocRoot makes you
irresistable to the opposite sex. It also cures athletes foot and stops
sniffles.
>>Also, documenting where a function is located ?<<
I like automatic documentation generators.
>>I'd like to hear agruments for and against.<<
Namespaces are great, as long as you do a bit of planning beforehand. You
don't really want to figure out which of 32 namespaces that function
DoSomethingReallyUseful() is in.
-Jacob
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org