03-08-2011
Thank you so much everyone for your responses. I finally solved the problem. For some reason, the Development System did not install correctly the first time. I re-installed it and now it compiles the old 4gl files.
Lesson learned: Start coding in a more "modern" language. LOL
Again thank you. Problem solved.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
For having shared file system i've been using nfs ,but regarding this i've some problem ,when i execute "df -ak" i can see the shared file system & i can also go there & list files ,but when i want to create anything in this area (Incld. file ,dir ....) i get permission denied. (i've shared related... (6 Replies)
Discussion started by: nikk
6 Replies
2. UNIX for Dummies Questions & Answers
i have the following entry in /etc/exports which is /opt/hpxt.
i am on hpux b11.0.0
questions
1) is /hpxt in the same physical machine? got confused by the meaning of export. (1 Reply)
Discussion started by: yls177
1 Replies
3. UNIX for Advanced & Expert Users
Setting up nfs on a redhat ES 4 gives me following issue that i
can't explain.
My nfs was working perfect whith following /etc/exports on the server
/home/test/nfstest 198.9.200.227(rw,sync,no_root_squash)
But after a powerloss and restart of the server it only works with the... (0 Replies)
Discussion started by: progressdll
0 Replies
4. AIX
Got a prob..
I am trying to export a directory and mount it on to a server using NFS. My exporting goes fine as I am able to see the shares through "exportfs -v"
But when I am trying to mount the directory on a the client.. I get an error..
"system call error number - 1"
pls help....
... (3 Replies)
Discussion started by: balaji_prk
3 Replies
5. UNIX for Dummies Questions & Answers
Dear expert,
My .bash_profile contain the following lines:
# User specific environment and startup programs
export CFLAGS="-I $HOME/.libstree/include";
export LDFLAGS="-L $HOME/.libstree/lib";
export LD_LIBRARY_PATH=/home/ewijaya/MyBioTool/libstree-0.4.2/lib:${LD_LIBRARY_PATH}
export... (1 Reply)
Discussion started by: monkfan
1 Replies
6. Shell Programming and Scripting
Dear expert,
My .bash_profile contain the following lines:
# User specific environment and startup programs
export CFLAGS="-I $HOME/.libstree/include";
export LDFLAGS="-L $HOME/.libstree/lib";
export LD_LIBRARY_PATH=/home/ewijaya/MyBioTool/libstree-0.4.2/lib:${LD_LIBRARY_PATH}
export... (1 Reply)
Discussion started by: monkfan
1 Replies
7. Programming
Is it possible to view all the functions exported by a given object file?
"dump -tv" comes the closest, but what exactly am I looking for to determine whether the symbol exists in the object file?
Essentially, I have a library that requires a call to "xdr_sizeof" and the compile is failing... (5 Replies)
Discussion started by: DreamWarrior
5 Replies
8. AIX
Why can I not add more than 1 filesystem to the /etc/exports file and export them via smitty, or command line?
I have tried, I stopped the NFS daemons, edited the /etc/exports file by hand, saved it, then re-started NFS, but it only still exports the first line in the exports file.
... (4 Replies)
Discussion started by: mrmurdock
4 Replies
9. AIX
Hello everyone
I need to share a file system with two Aix boxes, the version is 5.3 tl9.
I create the nfs and I can see the files from both servers, but the problem with one of them is that I can write on the file or If I create a new one I canīt.
On the server that I create the... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies
10. UNIX for Dummies Questions & Answers
Hi guys, I was asked to perform the following:
On server usdfslpsap04 following NFS mounts should be disabled
usdfslpwmt3:/u01/opt/wm6_data/ebiz_edi/CALIBER_data
50412232 13369544 34481872 28% /u01/opt/wm6_data/ebiz_edi/CALIBER_data
usauxoradw:/DWH/Transfer/current... (1 Reply)
Discussion started by: 300zxmuro
1 Replies
LEARN ABOUT OSX
moose::cookbook::snack::keywords
Moose::Cookbook::Snack::Keywords(3) User Contributed Perl Documentation Moose::Cookbook::Snack::Keywords(3)
NAME
Moose::Cookbook::Snack::Keywords - Restricted "keywords" in Moose
VERSION
version 2.0604
DESCRIPTION
Moose exports a number of sugar functions in order to emulate Perl built-in keywords. These can cause clashes with other user-defined
functions. This document provides a list of those keywords for easy reference.
The 'meta' keyword
"use Moose" adds a method called "meta" to your class. If this conflicts with a method or function you are using, you can rename it, or
prevent it from being installed entirely. To do this, pass the "-meta_name" option when you "use Moose". For instance:
# install it under a different name
use Moose -meta_name => 'moose_meta';
# don't install it at all
use Moose -meta_name => undef;
Moose Keywords
If you are using Moose or Moose::Role it is best to avoid these keywords:
extends
with
has
before
after
around
super
override
inner
augment
confess
blessed
Moose::Util::TypeConstraints Keywords
If you are using Moose::Util::TypeConstraints it is best to avoid these keywords:
type
subtype
class_type
role_type
maybe_type
duck_type
as
where
message
optimize_as
inline_as
coerce
from
via
enum
find_type_constraint
register_type_constraint
Avoiding collisions
Turning off Moose
To remove the sugar functions Moose exports, just add "no Moose" at the bottom of your code:
package Thing;
use Moose;
# code here
no Moose;
This will unexport the sugar functions that Moose originally exported. The same will also work for Moose::Role and
Moose::Util::TypeConstraints.
Sub::Exporter features
Moose, Moose::Role and Moose::Util::TypeConstraints all use Sub::Exporter to handle all their exporting needs. This means that all the
features that Sub::Exporter provides are also available to them.
For instance, with Sub::Exporter you can rename keywords, like so:
package LOL::Cat;
use Moose 'has' => { -as => 'i_can_haz' };
i_can_haz 'cheeseburger' => (
is => 'rw',
trigger => sub { print "NOM NOM" }
);
LOL::Cat->new->cheeseburger('KTHNXBYE');
See the Sub::Exporter docs for more information.
namespace::autoclean and namespace::clean
You can also use namespace::autoclean to clean up your namespace. This will remove all imported functions from your namespace. Note that
if you are importing functions that are intended to be used as methods (this includes overload, due to internal implementation details), it
will remove these as well.
Another option is to use namespace::clean directly, but you must be careful not to remove "meta" when doing so:
package Foo;
use Moose;
use namespace::clean -except => 'meta';
# ...
SEE ALSO
Moose
Moose::Role
Moose::Utils::TypeConstraints
Sub::Exporter
namespace::autoclean
namespace::clean
AUTHOR
Moose is maintained by the Moose Cabal, along with the help of many contributors. See "CABAL" in Moose and "CONTRIBUTORS" in Moose for
details.
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Infinity Interactive, Inc..
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.16.2 2012-09-19 Moose::Cookbook::Snack::Keywords(3)